> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.simchat.ai/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How staff access to content works

|| Staff access is managed through cohorts. See [Creating and managing cohorts](https://support.simchat.ai/en/article/creating-and-managing-cohorts-ril8fw/).

What your staff can see and edit is decided by their **role** and the **cohorts** they staff. This keeps different teams working on their own content - for example separate teams for anatomy, surgery and clinical skills - without everyone editing everything.
---

## How it works

* **Owners, administrators and assistant administrators** always see and edit everything, whatever the cohorts. Assistant administrators never see learner data
* **Usage managers** don't work on content at all - they manage the plan and minutes and see organisation-wide usage, whatever the cohorts
* **Cohort leads** author, review and publish content aimed at the cohorts they staff, and see those cohorts' learner data. Organisation-wide content is visible to them but read-only. AI behaviours follow their own rules - see below
* **Authors** see and edit content they created, content assigned to one of their cohorts, and content that isn't assigned to any cohort. They submit their work for review rather than publishing it themselves
* **Assessors** don't work on content at all - they review learner sessions for the cohorts they staff
* **Viewers** get the learner experience, published scenarios only, and are not affected by cohort staffing

Staffing a cohort also covers every sub-cohort nested inside it, so adding someone to a programme gives them every course beneath it. Content assigned to more than one cohort can be edited by the staff of any of them, so share a cohort only where shared editing is intended.

See [Understanding roles in SimChat](https://support.simchat.ai/en/article/understanding-roles-in-simchat-mrwfyo/) for what each role can do, or open **Staff → Roles explained** in SimChat for the full permission grid.
---

## Scoping an author, cohort lead or assessor to a cohort

1. Go to **Cohorts** and open the cohort
2. On the **Staff** tab, select **Add staff**
3. Choose the author, cohort lead or assessor

A staff member can staff more than one cohort. You can also assign cohorts when inviting staff, under **Cohorts they'll manage** on the invite form. Cohort leads must always be given at least one cohort.
---

## Assigning content to cohorts

Content is assigned through its access setting. On a scenario, set **Who can access this scenario?** to **Specific cohorts** in the **Key details** step, or use **Manage access** on the scenario list. Collections have the same setting.

Once assigned:

* The cohort's learners can access it, as can learners in any sub-cohort beneath it
* The cohort's staff can see it, and authors and cohort leads can edit it

Content that isn't assigned to any cohort stays visible to all of your authors, and to all learners if its visibility is set to everyone.
---

## Closing the catalogue: Only show assigned content

By default, learners see everything published to **All users in this organisation** as well as content assigned to their cohorts. To show learners only what has been assigned to them, turn on **Only show assigned content** under **Organisation settings → Policies**.

When it is on, learners, viewers and assessors see only the scenarios and collections assigned to their cohorts, or to a parent cohort. Content open to everyone is hidden unless it sits inside a collection assigned to their cohorts. Imported library scenarios are always organisation-wide, so put them in an assigned collection to reach a closed catalogue. Authoring views are unaffected.

|| With this setting on, a learner in no cohort sees an empty catalogue. Link your learner invite links to a cohort so new joiners are placed automatically, and use the **No cohort** filter and bulk **Add to cohort** action on the **Users** page to place anyone who isn't.
---

## Author policies

Under **Organisation settings → Policies**, administrators can narrow what the Author role may do on its own. Every switch is on by default, so nothing changes until you turn one off. These settings never restrict administrators, assistant administrators or cohort leads.

| Policy | On (default) | Off |
| ---- | ---- | ---- |
| **Authors can create collections** | Authors create collections | Only administrators create collections; authors can still add scenarios to collections they may edit |
| **Authors can delete content** | Authors delete the scenarios, collections and AI behaviours they may edit | Authors ask an administrator to delete, even for their own drafts |
| **Authors can make content available to everyone in the organisation** | Authors may choose **All users in this organisation** as an audience | Authors can only target specific cohorts; content already open to everyone stays that way until an administrator changes it |
| **Authors can edit organisation-wide content** | Authors edit any unpublished content not restricted to another cohort | Authors edit only their own work and content aimed at cohorts they staff; everything else is visible but read-only |
---

## Templates

Scenario templates have no cohort dimension, so only administrators and assistant administrators create, edit and delete them. Authors and cohort leads can start a new scenario from any template. See [Creating and managing scenario templates](https://support.simchat.ai/en/article/creating-and-managing-scenario-templates-78hjbs/).
---

## AI behaviours

AI behaviours have no cohort dimension. Instead, each one has a **Who can edit** setting:

| Setting | Who can edit it |
| ---- | ---- |
| **Administrators only** | Owners, administrators and assistant administrators |
| **Its creator and administrators** | The person who created it, plus owners, administrators and assistant administrators |
| **Authors and cohort leads** | Every author and cohort lead, plus owners, administrators and assistant administrators |

SimChat's default AI behaviours, and any created before this setting was introduced, are **Administrators only**. New ones start as **Its creator and administrators**.

The **Authors and cohort leads can create and edit AI behaviours** switch under **Organisation settings → Policies** is on by default. Turn it off and only owners, administrators and assistant administrators create and edit AI behaviours, whatever each one's setting says. Unlike the author policies above, this switch applies to cohort leads too.

Either way, everyone who creates scenarios can choose any AI behaviour for a scenario. Deleting an AI behaviour needs edit rights on it, authors also need **Authors can delete content** on, and an AI behaviour can't be deleted while any scenario, template or proposed update uses it.

Every change to an AI behaviour is recorded in its **edit history**, which anyone who can open the AI behaviours page can read, including for AI behaviours they can't edit. See [Creating custom AI behaviours](https://support.simchat.ai/en/article/creating-custom-ai-behaviours-5wyoxu/).
---

## Publishing

Authors submit their drafts for review. Administrators and assistant administrators can publish anything; a cohort lead can publish content aimed at their own cohorts. Live scenarios are locked below the administrator tier - cohort leads and authors use **Propose an update** instead, which goes through the same review. See [Submitting scenarios for review and publishing updates](https://support.simchat.ai/en/article/submitting-scenarios-for-review-and-publishing-updates-16nmp8t/).