Beyond their organization role, each person's access to a specific team, project, or assistant is set separately. This lets you give someone full control of one project while they only use another, and lets you decide which assistants everyone in the organization can find.Why access levels matter#
Collaborate safely. Let people use an assistant without letting them change or delete it.
Delegate ownership. Make a project lead an Admin of their project without giving them control of anything else.
Control discovery. Keep assistants in development Private, and make finished ones Public for the whole organization.
Admin and Member#
Every team, project, and assistant has two access levels: Admin and Member.Admin#
| Capability | Details |
|---|
| Manage | Edits settings and configuration, and manages who has access. |
| Delete | Can delete the resource when it's no longer needed. |
| Use | Has full use of the resource, for example chatting with an assistant. |
| Inheritance | Admin access to a project also gives Admin access to every assistant in it. |
Member#
| Capability | Details |
|---|
| Use | Views the resource and uses its main features, for example chatting with an assistant. |
| Limits | Can't delete the resource, change its settings, or manage other people's access. |
Choose Member for people who only need to use something, and Admin for the people responsible for it.
Assistant visibility#
Every assistant is either Private or Public.Private#
| Attribute | Details |
|---|
| Visibility | Only the assistant's owner, Global Admins, and people given access (directly, through its project, or through a team) can view it. |
| Best for | The default for new assistants. Use it while you build an assistant, or for sensitive work. |
Public#
| Attribute | Details |
|---|
| Visibility | Anyone within your organization can access the assistant. |
| Best for | Assistants meant for wide use, such as help desks or shared knowledge bases. |
| Sharing | Only Public assistants can be shared from the Share menu, including view-only links, view-and-edit links, and embedding. |
How access flows down#
1.
Organization roles: Global Admins automatically have Admin access to everything.
2.
Teams: If your team is added to a project as a Member, you get Member access to that project and every assistant in it.
3.
Projects: If you're added to a project as an Admin, you're an Admin of all its current and future assistants.
Use cases#
Building an assistant: While a contract-review assistant is being tested, keep it Private, with only the two lawyers building it as Admins. Nobody else can find it or change it.Rolling it out: When it's ready, make it Public so anyone in the company can find it, and add the paralegal team as Members so they can use it but not change its instructions.Project leads: Make a project lead an Admin of their project. They manage every assistant in it, without control of other projects. 