Skip to content
aYOUne

Action bar and notifications

Action bar and notifications

The action bar is a slim bar the Companion shows on web pages. It shows key figures from your wallboard and gives you quick actions, your notifications and the AI Copilot on every page, without leaving the page.

Turning the action bar on

The action bar is off after installation. To turn it on:

  1. Click the Companion icon in the Chrome toolbar and open Settings.
  2. In the Action bar section, switch on Show the action bar on every web page.
  3. Select a wallboard. Without a selected wallboard the action bar stays hidden – except on websites run with aYOUne (see below).

In the same settings you choose the position, pick the key figures and list sites where the action bar should never appear. To hide the action bar on a single site, click its ✕; you can switch it back on for that site in the popup.

The action bar only appears while you are signed in.

Docked or overlaid

From version 2.88 the action bar docks at the top: the website moves down by the height of the bar, and fixed headers (for example in Gmail, Outlook or LinkedIn) move with it. The bar no longer covers any content.

  • If the Companion notices that docking disturbs a page, it automatically switches to overlay there.
  • Use ⭱ / ⭳ in the action bar to choose for the current website yourself; your choice takes precedence.
  • Under Settings → Action bar → Docking per website you see all exceptions and remove them with ×.
  • Available positions: Docked at the top (default), Top overlay and Floating top right.

What the action bar contains

ElementWhat it does
Key figuresfigures from your wallboard, for example open orders or new contacts
Quick actionsNew contact · New task · New order · Insert text snippet · Run workflow · Open dashboard · Open wallboard
Notecapture a quick note; optionally assign it to a contact, where it then appears as an activity
Screenshotsave a screenshot of the current page
Copilotopen the AI Copilot in the side panel
Switch organizationshown when you have access to more than one organization
Pipeline statuswith DevOps access: shows whether the latest pipeline runs of your repositories succeeded; hidden without access
🚀 Start pipelinewith DevOps access and the right to start pipelines: a search field with your pinned (📌) and recently started repositories above it; find others via search (at most ten matches). A pipeline only starts after you confirm. The extension window now only shows the pipeline status.
⭱ / ⭳switch between “dock at the top” and “overlay” on this website
Refreshreload the figures
?open this help page

A connection indicator shows the state: Live, Offline, Disconnected or Sign in again.

On websites run with aYOUne, the action bar also shows a This page group with Edit page, Open website, Status page and Copilot for this page.

The labels inside the action bar are currently shown in German.

The bell

The bell counts your unread notifications. Click it to open the list:

  • the three newest notifications; more via show N more;
  • each notification is coloured by urgency (critical, warning, info) and shows a title, the time and a short text;
  • clicking a notification opens the related record in aYOUne in a new tab;
  • some notifications carry buttons, for example to approve or reject a browser-control step.

Opening the list marks all notifications as seen. The number of unread notifications also appears on the Companion icon.

Critical notifications and warnings additionally appear briefly as a message on the page, with an Open button and a Later button (shows the message again after 30 minutes). The Companion also uses your operating system's desktop notifications.

Notification settings

Under Settings → Notifications choose:

  • Always show (bell and pop-up)
  • Only on bell click
  • Off (desktop notifications only)

Under Mute notifications on list sites where neither the bell nor on-page messages should appear.

Urgent notifications, grouping, quiet hours

Since version 2.87.3 these switches are also under Settings → Notifications → On this computer, together with Desktop notifications (on by default): when off, the Companion shows new notifications only in the bell and on the web page, no longer as an operating-system notification.

You set your quiet hours and which notification types reach you on which channels centrally in aYOUne (My account → Notifications); they apply on all your devices. The Settings from aYOUne area shows the current state, for example "22:00–07:00, critical notifications still get through", and Edit in aYOUne takes you straight there.

Under Settings → Features (on by default since version 2.84, each can be switched off):

  • Sound and acknowledge for urgent notifications: a short sound for urgent notifications you may acknowledge; Acknowledge ends the alert on all your devices, including the aYOUne app.
  • Group similar notifications: one card with a counter per matter.
  • Respect quiet hours: no sound, pop-up card or full screen during your quiet hours; notifications still land in the bell.
  • Full screen for critical notifications: shows critical notifications large in the middle of the page. When off, a pop-up card appears at the edge instead.

The new tab

With the feature Overview in new tabs (on by default), a new tab becomes your start page: your upcoming appointments, your key figures, the latest notifications, what your AI employees are doing and what is waiting for you, your bookmarks from start.ayoune.app and a search field. When off, a new tab opens the aYOUne start page. More: Start page in the new tab.

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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/toolbar.md
The complete collection: https://ayoune.com/en/docs/companion.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)
Leave a comment