Notifications

aYOUne speaks up when something happens that concerns someone: a document is waiting for a signature, an employee has a birthday, someone is back from leave. Which of these occasions actually produce a message at your company is your decision.

Where to set this

Open Notification rules. You will see a list of occasions — each entry is a rule waiting for a particular event. The list of notification rules

Every rule shows you three things:

the occasion, for example Document waiting for signature (reminder)
the area the event comes from, for example Documents or HR
whether it is active

Adjusting a rule

Click the rule. Inside it you decide who gets notified and through which channel the message goes out.

One occasion can have several recipients, and the same occasion can reach different people by different routes. The manager gets an email, the team gets a message inside the application — that is an entirely ordinary setting, not a special case.

Switching a rule off

You do not have to delete a rule to get some quiet. Set it to inactive; it is then kept and you can switch it back on later without creating it again.

That is the better route when you only need an occasion paused for a while — company holidays and leave notifications, for instance.

What everyone sets for themselves

Alongside the company-wide rules, every person has their own notification settings in their profile. That is where they decide what they personally want to hear about.

This matters when someone comes to you saying they get too many or too few messages: check the personal profile first, before you touch the company-wide rules. A change there affects everyone.

A good starting point

Start with few active rules and switch on whatever turns out to be missing. The opposite route — switch everything on and then weed it out — reliably ends with messages going unread and the important ones drowning among them.

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Explain what I need this for What it is good for — and when it is worth it.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Explain to me what I need this for.

1. Which problem does it solve? In one sentence, from my point of view.
2. Three typical situations in which it genuinely helps me.
3. When I do NOT need it — that saves me time.
4. What I can do instead if it is not a fit.

Stick to what the source says. Where it gives nothing, say so openly instead
of guessing.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Help me set this up Step by step, asking me as you go.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Help me with a problem Narrow down the cause instead of guessing.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Explain it in plain words No jargon, from the ground up.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

A checklist to tick off To follow along while you do it.

Open in ChatGPT

Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/notifications.md
The complete collection: https://ayoune.com/en/docs/admin-handbook.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)