Members
Project membership controls who can see and modify this project. Every member has a role; the role decides which actions they can perform. Adding the right people with the right roles is usually the difference between a project that’s safe to share with stakeholders and one where a misclick deletes a tool.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including transferring ownership and deleting the project. Owner is the only role that can delete; demote with care. |
| Admin | Project, member, document, conversation, analytics, tools, and sub-project management. Cannot delete the project or transfer ownership. Use this for operational leads. |
| Viewer | Read-only across the project (any *.view permission). Can read conversations, see analytics, inspect tools — but can’t change anything. Use this for stakeholders, auditors, or new team members during onboarding. |
For finer-grained access (e.g. “can edit documents but not tools”), create a custom role from Dashboard → Roles by composing permissions from the catalog (project, documents, conversations, analytics, members, sub-projects, tools).
Invitation Lifecycle
Invitations are sent by email and also surface in the invitee’s Invitations page. They expire after a fixed window if not accepted; an unaccepted invitation can be cancelled at any time before it’s accepted.
When you change a member’s role, the change applies on their next request — no re-login required. When you remove a member, their access revokes immediately and any in-progress dashboard session is cut off on the next action.