People and access
Department access
Choose which departments each person sees, and what a limited person sees and is refused.
# Department access By default, everyone sees every department. An admin can limit a person to a fixed set of departments. ## Set access (admin only) Open **Settings**, then the **People** tab. Each person has a row: their name and job title, their role, how far they have come, and what they see, which is their departments, "All departments" or "No departments". To find someone, use the filters above the list (**All**, **Admins**, **Members** and **Invited**, each with a count) or search by name or job title. Click a name to see that person's details, including their email or user ID. Where you can't change them (the owner, or another admin when you are an admin), the details are read-only. To change what a member sees, click the departments in their row, or click their name to open their details. Then: - Turn on **All departments** to let them see every department, including departments added later. - Or turn it off and untick the departments they should not see. Turning it off keeps every department ticked, so nothing changes until you untick one. - Choose **Save**, or **Save Changes** if you opened their details. If a change is refused, the reason shows on that person's row. Admins see every department and every company app, so their row says "Everything". A person with no departments ticked sees the Company Brain only. ## What a limited person sees - The skill tree shows only the allowed departments. - The team rail lists the Company Brain and the agents for the allowed departments. The Company Brain stays, but carries only the allowed skills. - The list of skills the brain offers in a chat covers only allowed skills. ## What a limited person is refused - Starting a chat with a skill or agent outside their set is refused with a message. - The brain refuses to load a skill, read a skill's files or run a skill's script that is outside their set. It tells the person it cannot, and carries on. ## What this does not do Department access sets skills and agents, and it counts for any app whose audience is those departments. What each app and uploaded files share, and with whom, is set per app, so All Departments does not open an app set to Admins Only. See [Connected apps](https://docs.skilltreeos.ai/connected-apps/) and [Knowledge](https://docs.skilltreeos.ai/knowledge/).By default, everyone sees every department. An admin can limit a person to a fixed set of departments.
Set access (admin only)
Section titled “Set access (admin only)”Open Settings, then the People tab. Each person has a row: their name and job title, their role, how far they have come, and what they see, which is their departments, “All departments” or “No departments”. To find someone, use the filters above the list (All, Admins, Members and Invited, each with a count) or search by name or job title. Click a name to see that person’s details, including their email or user ID. Where you can’t change them (the owner, or another admin when you are an admin), the details are read-only.
To change what a member sees, click the departments in their row, or click their name to open their details. Then:
- Turn on All departments to let them see every department, including departments added later.
- Or turn it off and untick the departments they should not see. Turning it off keeps every department ticked, so nothing changes until you untick one.
- Choose Save, or Save Changes if you opened their details.
If a change is refused, the reason shows on that person’s row.
Admins see every department and every company app, so their row says “Everything”. A person with no departments ticked sees the Company Brain only.
What a limited person sees
Section titled “What a limited person sees”- The skill tree shows only the allowed departments.
- The team rail lists the Company Brain and the agents for the allowed departments. The Company Brain stays, but carries only the allowed skills.
- The list of skills the brain offers in a chat covers only allowed skills.
What a limited person is refused
Section titled “What a limited person is refused”- Starting a chat with a skill or agent outside their set is refused with a message.
- The brain refuses to load a skill, read a skill’s files or run a skill’s script that is outside their set. It tells the person it cannot, and carries on.
What this does not do
Section titled “What this does not do”Department access sets skills and agents, and it counts for any app whose audience is those departments. What each app and uploaded files share, and with whom, is set per app, so All Departments does not open an app set to Admins Only. See Connected apps and Knowledge.