Roles are set per Project

- Owner — Full admin access (including sharing and settings).
- Collaborator — Can chat and add Knowledge.
- Reader — Can read chats and Knowledge.
How people join

- Invite by Email — Send a personalized invitation to specific colleagues at a chosen role.
- Share a Secret Link — Anyone who opens the link is added to the Project at the role you set on the link.
- Domain Access — Anyone with an email address from a domain you add automatically sees the Project. This is how you grant company-wide access.
ℹ️ Good to Know: Chief doesn’t have a separate org-level members roster with seats to assign. Org-wide access comes from domain-based joining plus per-Project roles — not a per-seat license you allocate.
Removing access
To cut off a whole domain, remove that domain under Domain Access — every user with that email domain loses access to the Project. To revoke a secret-link invite, delete that secret link; everyone who joined through it loses access. See Removing members and managing access for the exact steps.Frequently asked questions
I removed someone but they can still get in. Why?
I removed someone but they can still get in. Why?
They probably have access through more than one path — for example, both a domain grant and an email invite. Check the Current Members list to see how they joined, and remove each path that applies.
Where is the org-wide member list?
Where is the org-wide member list?
Membership lives on each Project, not in one central org roster. Organization settings cover General, Memory, and Integrations; to manage people, open the relevant Project’s Share this Project panel.
What role does a secret-link joiner get?
What role does a secret-link joiner get?
The role you choose when creating the link — Owner, Collaborator, or Reader. Everyone who joins through that link gets that role.