Expected outcome
The approved access matches one person or integration, one workspace, and one documented job.
Tempera is in private preview and provides private APIs across its product areas. Access is arranged through onboarding for an agreed evaluation, with product-specific credentials, endpoints, and environment details supplied directly to your team. API maturity ranges from preview to research, and no shared cross-product endpoint is implied.
Before you start
- A provisioned workspace
- A written description of the job being approved
Steps
- 01
Name the job first
Write down what the person or client must do before selecting a role or permission.
- 02
Choose the workspace
Confirm the organization, project, and environment in human terms. Do not approve access while the selected workspace is unclear.
- 03
Approve the smallest useful set
Select product permissions that match the job. Keep administrator access separate from ordinary browser, trace, or review work.
- 04
Test and revisit
Run one narrow task, then remove permissions that were not needed. Revoke the connection when the job or owner changes.
What success looks like
- The owner can explain every approved permission.
- The connection cannot silently move into another workspace.
- Revocation affects the intended connection without requiring a broad credential rotation.
If something is blocked
- If a task is blocked, identify the missing action before adding a permission.
- If raw workspace identifiers are the only context shown, stop and ask the workspace owner to confirm the selection.
- If administrator access seems required for routine work, review the job and product permissions before approving it.