How to promote an agent or output template from Private to Workspace or Organisation

What you'll learn

When you create an agent or output template in Assist, it always lands in your Private space first. To make it usable by your team — or by everyone in the organisation — you need to promote it. This article walks through exactly how.

In this article:

Why agents and templates start in Private space
The difference between Workspace and Organisation tiers
How to promote an item, step by step
How to choose the right tier
Common pitfalls to avoid

Quick recap: the three tiers

Every agent and output template in Assist lives at one of three tiers:

Private — only you can see and use it. This is where all new agents and templates land by default.
Workspace — visible to everyone in your current workspace. Best for team-specific tools.
Organisation — visible across every workspace in the org. Best for assets that genuinely benefit everyone.

Promotion is one-way when done through chat or the Library: Private → Workspace, Private → Organisation, or Workspace → Organisation. If you ever need to move an item back down a tier, you'll need to manage that manually in the Library.

Before you promote — a quick check

Before sharing an agent or template with your team, test it in your Private space first. Run it a few times, refine the instructions, and make sure it does what you expect.

Promoting an unfinished agent or template is the most common cause of "this doesn't quite work" feedback from teammates. A little testing upfront saves a lot of confusion later.

How to promote an item

Open the Library from the left-hand nav.
Use the tier filter to switch to Private (or Workspace, if you're promoting from workspace to org).
Find the agent or output template you want to promote.
Open it and select Promote.
Choose the destination tier — Workspace or Organisation.
Confirm. The item now lives at the new tier and follows that tier's permissions.

That's it. Your teammates will be able to find and use it straight away.

Choosing the right tier

Not sure which tier to pick? Here's a simple rule of thumb:

Default to Workspace for anything team-specific — a brand voice agent, a project brief template, an internal reporting doc, and so on.
Use Organisation sparingly — only for assets that clearly benefit every team across the org, like a company-wide tone-of-voice agent or a universal meeting-notes template.
When in doubt, start at Workspace. You can always promote further later. It's much easier to expand access than to walk it back.

Worked example: the Brand Tone Checker

Say you've built a "Brand Tone Checker" agent in your Private space. You test it on a couple of pieces of copy, tweak the instructions, and once you're happy with how it performs, you head to Library → Private, open the agent, and select Promote → Workspace.

Your teammates can now @ -mention it directly in chat — no extra setup needed on their end.

A few weeks later, another team in the org asks if they can use it too. You go back to Library → Workspace, open the agent, and select Promote → Organisation. It's now available across every workspace in the org.

Tips & common pitfalls

"My teammate can't @-mention the agent I made."

Almost always means the item is still in Private space. Head to Library → Private, find the agent, and promote it. Once it's at Workspace or Organisation tier, teammates can @ -mention it straight away.

Skills are different.

Skill creation and promotion is admin-gated and doesn't follow the same Private → Workspace → Organisation flow. If you're working with skills, check with your workspace admin.

Promotion through chat is one-way.

If you need to demote an item — for example, taking an org-tier template back down to workspace — do it in the Library directly. You can't reverse a promotion through a chat command.

Promote when ready, not before.

Test in Private first. Promoting a half-finished agent is the most common source of confusion for teammates, and it's easy to avoid.

Naming matters at higher tiers.

Once an item is visible at workspace or org level, give it a clear, descriptive name. Other people need to understand what it does at a glance — especially if they're browsing the Library or searching for something to @ -mention.