> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackmountain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Visibility and Governance

> Control who can share, use and edit assistants, prompt templates, toolsets and skills

Members build their own assistants, prompt templates, toolsets and skills, and can share them with colleagues. The organization hierarchy and member roles decide how far something can be shared and who may change it. This page explains the rules, so you can set up roles that match how your company wants to share.

## Visibility scopes

Assistants, prompt templates and toolsets have four visibility options:

| Visibility | Who can use it |
| - | - |
| **Private** | Only the creator |
| **Team** | Every member of the chosen team |
| **Workspace** | Every member of the chosen workspace and its teams |
| **Organization** | Every member of the organization |

Viewers can use everything shared with them. Using a shared item never requires a higher role.

## Who can share and edit

| Action | Who |
| - | - |
| Create a private item | Every member |
| Share with a team, workspace or organization | Owners and Managers of that team, workspace or organization |
| Edit or delete a shared item | Its creator, plus Owners and Managers of the scope it's shared with |
| Use a shared item | Everyone in the scope, including Viewers |

Roles are inherited down the hierarchy. A Manager of the organization can share with and edit content in every workspace and team. A Manager of one workspace can do so only in that workspace and its teams. See [Roles and permissions](https://docs.blackmountain.io/admin/organization/roles-and-permissions.md).

Members who can use but not edit an assistant open it read-only. 48° tells them that only the creator or a Manager or Owner of its scope can make changes.

> [!TIP]
>
> To control what reaches everyone, keep organization-wide Manager roles to a small group. Give Manager roles at workspace or team level to the people who curate assistants for that area.

## Skills

Skills follow simpler rules:

| Visibility | Who can use it | Who can edit it |
| - | - | - |
| **Private** | Only the creator | Only the creator |
| **Team** | Members of the chosen team | Only the creator |

* A member can share a skill with any team they are a direct member of. No Manager role is needed.
* Team members get read-only access. Nobody but the creator can change a skill, including Owners and Managers.

### Skills on assistants

A skill attached to an assistant must reach at least as many people as the assistant:

* A private assistant can use any skill its creator can see.
* A team assistant can only use skills shared with that same team.
* Workspace and organization assistants can't use skills.

If a skill doesn't fit, 48° lists the skills that are shared with fewer people and asks you to share them with the same team or remove them.

## Things to know before sharing

* **Prompt templates on assistants.** When you attach a prompt template to an assistant, its text becomes visible to everyone who can use the assistant, even if the template itself is shared more narrowly. 48° warns before this happens.
* **Toolsets on assistants.** An assistant's toolset only works for people who can use that toolset. Others can use the assistant, but without those tools. Each member also needs their own connection to the integrations in the toolset.
* **Deleting an assistant** also deletes its reference files. Chats that used it remain, without the assistant.
* **Deleting a team or workspace** also deletes the assistants and prompt templates shared with it. Toolsets and skills shared with a deleted team become private to their creator, and chats shared with it are no longer shared.

## Feature access

Some features depend on your plan. If a sidebar entry shows a **Pro** badge, or Skills or the Editor are missing for your organization, contact BlackMountain support. Writing skills also needs the Editor.

## A simple governance model

**1. Decide who curates**

Pick a few people per department who build and maintain shared assistants. Make them Managers of their workspace or team.

**2. Keep organization-wide content small**

Share only well-tested, general-purpose assistants and templates with the whole organization.

**3. Let teams experiment**

Members can build private assistants and share skills with their own team. Promote the good ones to a wider scope later.

**4. Review regularly**

Check shared assistants and templates every few months, and remove those nobody uses.

## Related

> [card] [Assistant visibility and sharing](https://docs.blackmountain.io/assistants/visibility-and-sharing.md)
>
> The member's guide to sharing assistants.

> [card] [Sharing skills](https://docs.blackmountain.io/editor/skills/sharing-skills.md)
>
> How members share skills with a team.

> [card] [Toolsets](https://docs.blackmountain.io/admin/integrations/toolsets.md)
>
> Bundle integration tools for assistants.

> [card] [Sharing controls](https://docs.blackmountain.io/admin/security/sharing-controls.md)
>
> Control how chats are shared.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.