Expected outcome
Claude Code 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 Code use case
- A workspace owner who can review requested permissions
Steps
- 01
Confirm the job and workspace
Write down what Claude Code 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
Tool invocation covers the approved development tools; evaluation execution covers the named staging evaluation. Add trace or dataset access only if a separate reviewed task requires it.
- 04
Run the client-specific check
Run one agreed evaluation against an inert staging case, then confirm the result belongs to the intended workspace.
What success looks like
- Claude Code shows as connected for the selected workspace.
- The approved permissions match the documented job.
- Claude Code can run the named staging evaluation without broader data 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.