> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/roles-settings-and-help.md).

# Roles, Settings and Help

Every control in the CMS is tied to a permission, so the same dashboard renders differently depending on the scopes the signed-in user carries.

## 25. The UI adapts to your role

Every control in the CMS is tied to a permission, so the same dashboard renders differently depending on the scopes the signed-in user carries. A viewer sees the content but no way to change it; an editor gains the authoring actions; an administrator additionally gets Settings. This chapter signs in as each of the three roles in turn and shows the toolbar and header adapting — the create actions and the Settings button appearing exactly when the role allows.

### 25.1 A read-only viewer can browse, but has no authoring or admin controls

Signed in with a read-only role, the dashboard is a reading room. Every content tab — Pages, Layouts, Themes, Components, Media — is here to browse, and any page opens for inspection. What is missing is everything that changes state: there is no New Page button in the toolbar, and no Settings in the header. A viewer sees the whole library; they simply cannot alter it.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-6400e98a2ee5ab603748a6a7788036844a8a80ef%2Fcms_ug_p66_1.png?alt=media" alt="25.1 A read-only viewer can browse, but has no authoring or admin controls"><figcaption><p>25.1 A read-only viewer can browse, but has no authoring or admin controls</p></figcaption></figure>

### 25.2 An editor gains the authoring actions — but still no Settings

An editor's role adds the write scopes, and the authoring controls appear with them: the toolbar now offers New Page (and New Folder), and the same create, publish and delete actions return across the other tabs. Settings stays absent — administering the tenant is a separate, higher privilege. This is the everyday content role: full authoring, no configuration.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-966debc1bcb3ecf182f6457375f76190b1d37833%2Fcms_ug_p67_1.png?alt=media" alt="25.2 An editor gains the authoring actions — but still no Settings"><figcaption><p>25.2 An editor gains the authoring actions — but still no Settings</p></figcaption></figure>

### 25.3 An admin sees everything, including Settings

An administrator holds the override scope, so nothing is hidden: every authoring action is present, and the Settings button returns to the header — the door to tenant configuration, schema provisioning and the rest. Where the editor could shape content, the admin can also change how the CMS itself is set up.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-52580d2dce174cf59e89e3e4ef11fb94e74de8de%2Fcms_ug_p68_1.png?alt=media" alt="25.3 An admin sees everything, including Settings"><figcaption><p>25.3 An admin sees everything, including Settings</p></figcaption></figure>

## 26. Settings — a tour

Settings is where the tenant's admin configures the CMS itself: which storefront the preview iframe points at, whether approval is required before publish, secret keys, and so on. Every author's dashboard has a Settings link — only admins land somewhere useful.

### 26.1 Settings is a top-level route reached from the dashboard header

Settings is organised into tabs — Preview (which storefront to frame), Approval (whether publishing requires review), Secrets (API keys), Domains, and so on. Every change affects the whole tenant; per-page overrides live on the page itself.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-3fcdf5438cbc87f1c75485411f0e648ee98a2fbe%2Fcms_ug_p69_1.png?alt=media" alt="26.1 Settings is a top-level route reached from the dashboard header"><figcaption><p>26.1 Settings is a top-level route reached from the dashboard header</p></figcaption></figure>

## 27. Help — the in-app reference

Every CMS screen carries a Help launcher in the bottom-right (next to the AI assistant, when configured). It opens a compact reference of common tasks plus the permission scope catalog. Content is driven by the `help` i18n namespace — the manual and the in-app help come from the same source of truth, so the two agree by construction.

### 27.1 A persistent Help button lives in the bottom-right

The launcher sits above the app's footer strip and just left of the AI chat launcher. It's on every screen — dashboard, editor, settings — so a stuck author never has to hunt for it.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-5fc618ee3c78f43368b0ed63ed8e52cd63baf72d%2Fcms_ug_p70_1.png?alt=media" alt="27.1 A persistent Help button lives in the bottom-right"><figcaption><p>27.1 A persistent Help button lives in the bottom-right</p></figcaption></figure>

### 27.2 Clicking it opens a scrollable reference panel

The panel has two sections: task how-tos (create a page, submit for approval, use layouts, translate content) and a scope catalog. Both are localised — the panel reads the current SPA language and picks matching strings.

<figure><img src="https://270962768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaAxCFK0JJRlhIPufuXz8%2Fuploads%2Fgit-blob-a02ce59293d856d2cf12c4c2deed15626a60d144%2Fcms_ug_p71_1.png?alt=media" alt="27.2 Clicking it opens a scrollable reference panel"><figcaption><p>27.2 Clicking it opens a scrollable reference panel</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/partner-library/partner-components/medienwerft-cms/user-guide/roles-settings-and-help.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
