Access review and incidents
Review who and what can reach the workspace, and respond when access is exposed.
- WhoOwners and admins
Run a workspace access review
- 1.
Review workspace members
Remove people who no longer need access and assign the lowest role that supports each person's work.
- 2.
Review project boundaries
Check restricted-project membership, private docs spaces, portal guests, and external review links separately from workspace roles.
- 3.
Review machine access
List workspace API keys, service accounts, webhooks, installed integrations, and personal tokens approved for the workspace. Revoke unused credentials and rotate any secret that may have been exposed.
- 4.
Record the review
Use the workspace activity log, where your plan includes it, for member, sign-in, and setting events. Write down the review date, owner, exceptions, and follow-up work.
Respond to exposed access
- A member account may be compromised
- Remove the member or change their role, have them sign out other devices, and review recent workspace activity. Rotate credentials the account could read.
- A public or portal link was exposed
- Revoke or replace the affected share or portal link, then verify the old URL no longer opens. Review shared content and guest activity for unexpected access.
- An API key or webhook secret was exposed
- Revoke or rotate the credential immediately, update every authorized consumer, and monitor failed and successful requests during the cutover.
- You need a record for an investigation
- Note timestamps, affected people, and resource links before routine cleanup. Do not share tokens, email codes, or raw secrets in support messages.
If you cannot tell who created an exposed credential, revoke it and issue a replacement.
Role permissions are listed in workspace roles.