Access decisions should match the task. CentralizeMe documents project-scoped roles, scoped access to specific secrets or resources, and temporary guest or link-based access for collaborators who do not need a permanent relationship with the project.
Scope access to the task#
Start with the smallest useful scope. A teammate may need access to a project or a specific resource; a contractor may need a guest account or a link for a bounded engagement. Review the scope before sharing and again when the task changes.
The access model is backed by WorkOS authentication and project-scoped roles. The precise controls available to an account can depend on its current product configuration, so document the intended scope in the grant rather than relying on an informal message.
Use temporary access for bounded work#
For temporary work, the grantor sets the scope and duration. Guest and link-based access are documented with automatic expiry, so the access window closes when its duration ends. Treat expiry as a deliberate boundary: confirm that the work is complete, review what was accessed, and follow any post-expiry rotation reminder.
Temporary access is not a substitute for a clear owner. Record why the access exists, who granted it, and when it should end. If the task continues, review the grant instead of silently extending a broad permission.
Revoke access and review the trail#
When access is no longer needed, revoke the grant through the project’s access controls. Revocation changes the access decision; it does not by itself replace a credential. If a credential may have been exposed, use the rotation workflow and its usage inventory or checklist as a separate follow-up.
The documented audit trail records reveals, copies, rotations, shares, grants, and revocations with the actor, action, target, and timestamp. Use that record to confirm that the intended grant and revocation occurred and to give the next reviewer a concrete history.
Verification checklist#
Before you consider a sharing change complete, verify:
- The recipient, project, resource scope, and reason are clear.
- A temporary grant has an explicit duration and an expected expiry.
- The grant is revoked when the task ends, rather than left to an informal reminder.
- The audit trail shows the relevant grant, share, access, or revocation event.
- Any potentially exposed credential is handled through rotation as well as access review.
For the underlying isolation, encryption, secret-value boundaries, and compliance posture, read Security & Architecture.