aYOUne

Brand

Your people should see your brand when they sign in, not somebody else's. Everything you need for that sits together in one place.

Where to set this

Administration → Company → Brand

The Company page has three tabs: General, Legal and Brand. The third one is what this chapter is about. The Brand tab with the fields for logo, icon, brand name and slogan

What you provide

Logo and icon, twice each

You provide four images, and the reason is simple: some of your people work with a light appearance and some with a dark one, and a logo that looks good on white disappears on black.

Field What for
Logo light The full wordmark on a light background
Logo dark The same wordmark for the dark appearance
Icon light The short form — for narrow bars and the browser tab
Icon dark The same short form for a dark background

Each field has its own Upload logo or Upload icon; you remove an image already in place with the bin symbol next to it.

If you only have one version: put it in both fields. That is better than leaving one empty — empty means no logo appears in that spot at all.

Brand name and slogan

Below that are two text fields:

  • Brand — the name you trade under. It may differ from your registered company name, and that is exactly what the field is for.
  • Slogan — the line that sits below the name.

Where to start

The order that causes the least rework:

  1. First Logo light and Icon light — that is the default most people see.
  2. Then the dark versions.
  3. Finally Brand and Slogan.

After saving, it is worth a look with both the light and the dark appearance. The most common mistake is a dark logo that has accidentally ended up in the dark field too, where it becomes invisible.

Company details and legal

The other two tabs belong to the same task even though they have nothing to do with looks:

General carries company name, email, phone, website and address. One field there deserves attention: the industry. It decides which modules are suggested to you on the start page — so a wrongly set industry leads to recommendations that do not fit. The General tab of the company details

Legal takes the details that appear in your documents and mailings.

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

This page: https://ayoune.com/en/docs/admin-handbook/branding.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/branding.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/branding.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/branding.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.
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/admin-handbook/branding.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)
Leave a comment