Expected outcome
Claude can perform the agreed job in the selected workspace without receiving broader access than it needs.
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 design-partner workspace
- An approved Claude use case
- A workspace owner who can review requested permissions
Steps
- 01
Confirm the job and workspace
Write down what Claude needs to do and which staging workspace contains the permitted data.
- 02
Use the supplied connection details
Use the client registration, sign-in link, or configuration supplied during onboarding. Tempera does not publish a shared endpoint or generic public configuration in this guide.
- 03
Match permissions to this job
Approve tool invocation only for the tools in the agreed job and trace reading only for its evidence. Do not add write, evaluation, or administrator access for a review-only workflow.
- 04
Run the client-specific check
Ask Claude to inspect one known staging trace and identify the decision point without changing the source record.
What success looks like
- Claude shows as connected for the selected workspace.
- The approved permissions match the documented job.
- Claude can read the intended trace evidence without receiving write or administrator access.
If something is blocked
- If the connection is expired or revoked, reconnect the same client instead of creating a broader credential.
- If a permission is missing, request only that permission and repeat the narrow check.
- If the wrong workspace appears, stop before running a tool and reconnect from the intended workspace.