Visibility scopes
Assistants, prompt templates and toolsets have four visibility options:
Viewers can use everything shared with them. Using a shared item never requires a higher role.
Who can share and edit
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.
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.
Skills
Skills follow simpler rules:- 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.
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
Assistant visibility and sharing
The member’s guide to sharing assistants.
Sharing skills
How members share skills with a team.
Toolsets
Bundle integration tools for assistants.
Sharing controls
Control how chats are shared.

