Skip to main content
tempera

Provisioned private-preview workspace required

Connect Tempo during onboarding

Prepare Tempo for browser sessions and, when Palette is also in scope, a separately configured evidence path with connection details supplied for your private evaluation.

Expected outcome

Tempo 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 Tempo use case
  • A workspace owner who can review requested permissions

Steps

  1. 01

    Confirm the job and workspace

    Write down what Tempo needs to do and which staging workspace contains the permitted data.

  2. 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.

  3. 03

    Match permissions to this job

    Tempo session access and Palette trace and evaluation access are separate. Grant trace writing and evaluation execution only for the explicitly referenced Palette record and named quality check configured during private onboarding. These permissions do not create or infer a Tempo-to-Palette match. Keep unrelated dataset, unmasking, and administrator permissions out of this connection.

  4. 04

    Run the client-specific check

    Open one approved Tempo session. If Palette is in scope, verify the onboarding-configured reference against both the Tempo session and intended Palette trace before running the named quality check. Do not infer a match from timing or similar content.

What success looks like

  • Tempo shows as connected for the selected workspace.
  • The approved permissions match the documented job.
  • The explicit reference configured during onboarding is checked against the intended Palette trace; correlation is not automatic, and unrelated dataset or administrator access is absent.

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.