Workspace and organization administration
Workspace access follows the authenticated user and workspace or organization boundary. In an organization, administrators can manage organization membership, invitations, and roles through the organization controls.
Use the least authority necessary:
- Give members access only to the workspace and information they need.
- Restrict administrative roles to people who manage membership, settings, or high-impact actions.
- Review organization invitations and member roles regularly.
- Remove access promptly when a contractor, client engagement, or employment relationship ends.
API keys
Open Settings → API keys to create and manage API keys.
| Permission | Access |
|---|---|
workspace:read | Read project data. |
workspace:write | Modify project data. |
strategy:read / strategy:write | Read or modify project strategy. |
content:read / content:write | Read or create and modify content. |
reports:read | Read reports. |
admin | Full access. Use sparingly. |
Prefer a project-scoped key over a multi-project key whenever possible. The secret value is shown only when created. Store it in a proper secret manager or the approved tool environment, not in a page, chat, uploaded file, screenshot, or source code repository.
Revoke a key immediately if it may have been exposed, is no longer needed, or belongs to a departing collaborator. You can also delete a revoked key to remove it from the list.
Account and sharing security
- Use the account security controls for your personal account security settings.
- Use Settings → Shared links to audit what is externally accessible right now.
- Treat public links as public. Do not rely on obscurity of the URL as a security control.
- Rotate a link by changing its audience or revoke it and create a new link.
- Use organization-only links when the material is intended only for your organization.