How to share your work in Assist 2.0

Please note: some clients may have custom permissions configured by their account manager. If your setup differs, please consult your account manager for details.

You've created something great, and now it's time to share it with your team. Assist 2.0 is built on the principle of "privacy by default," meaning you are always in complete control of who sees your work. This guide will walk you through how to share your workspaces, projects, templates, and agents securely and effectively.

The Core of Sharing: Workspace & Project Roles

Sharing happens at the level of a specific Workspace or Project. When you create a new item, you are its owner. To bring collaborators on board, you simply need to share it with them and assign one of three distinct roles.

Choose a role based on the level of access you want each person to have:

Admin: This role grants the highest level of access to your specific item. An Admin can do everything you can, including renaming the workspace or project, managing its settings, and sharing it with even more people.

Best for: Co-leaders, project managers, or trusted collaborators who need full control.

Creator: A Creator can actively contribute new content. For example, they can create new projects within a shared workspace, add new outputs within a shared project, or build templates and agents for the team to use. However, they cannot change the item's core settings or manage its permissions.

Best for: Team members who need to add their own work and collaborate on content.

Viewer: This is a "read-only" role. A Viewer can see all the contents of the workspace or project but cannot create, edit, or change anything.

Best for: Stakeholders, clients, or team members who need to review progress without making changes.

Templates and Agents

Templates and agents work a little differently from projects — they aren't shared person-by-person. Instead, their visibility is controlled in one of three ways:

Public or private within a workspace: When you (or Assist) create a template or agent, you can set it to private (only you can see it) or public (visible to everyone in that workspace).

Org templates and agents: An Organisation Admin can publish a template or agent at the organisation level, making it available to everyone across every workspace in your organisation. These appear alongside the built-in ones in the marketplace.

Across workspaces or organisations: Templates and agents can't be shared directly between workspaces or orgs. To use one elsewhere, clone it into the destination workspace — you'll get your own copy to use and adapt.

Understanding Your Overall Role in the Organisation

While you control sharing for your individual projects, every user also has a role at the higher Organisation level. This role, either Member or Admin, defines your baseline capabilities across the entire platform.

Member: This is the standard user role with access to create and collaborate on the work they own or have been invited to.

Organisation Admin: This role has the highest level of access across the whole organisation. An Organisation Admin can perform exclusive actions like:

• ➕ Adding knowledge, templates, and agents that are available to everyone.
• 📊 Viewing platform-wide usage reports.
• 🔐 Managing the organisation's primary workspace.
• 🛠️ Approving custom skills (where enabled).

It's important to know that even an Organisation Admin cannot see your private work unless you explicitly share it with them.

Privacy First: Your Work is Secure by Default 🔒

We believe your work should be yours alone until you decide otherwise. Here's how our privacy-first approach protects you:

Private by Default: When you create a new workspace, project, template, or agent, it is visible only to you.

Explicit Sharing Required: To give anyone — even an Organisation Admin — access to a project or workspace, you must manually share it with them. Templates and agents stay private until you switch them to public in the workspace, or until an Org Admin publishes them organisation-wide.

Workspace-Scoped: Knowledge, projects, and chats stay within the workspace they were created in. Nothing leaks between workspaces, even within the same organisation — if you want a template or agent in another workspace, clone it across.

For teams that prefer a more open environment, you can streamline your workflow by changing your default settings. You can configure your account to automatically grant a specific access level (e.g., Viewer) to everyone in your organisation whenever you create something new. This can also be set up for you by your account manager.