Expected outcome
The affected access is removed and the owner can verify which other connections remain active.
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
- The person, client, session, or key that should lose access
Steps
- 01
Identify the smallest affected item
Choose the specific session, client connection, teammate, or key instead of rotating everything first.
- 02
Revoke or end it
Use the matching workspace control to remove that access.
- 03
Confirm the result
Check that the affected item is no longer active and that unrelated work still functions.
- 04
Replace only when needed
Create a new narrow credential only if the approved integration still requires one.
What success looks like
- The affected access no longer works.
- Unrelated connections remain unchanged.
- The workspace record shows who made the change and when.
If something is blocked
- If a client still appears active, clear its local session and contact the onboarding team with the connection name.
- If the affected item cannot be identified, pause the integration and ask the workspace owner to review active access.