Expected outcome
The teammate joins the correct workspace without sharing another person's credentials.
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
- The teammate's work email and intended role
Steps
- 01
Confirm the active workspace
Read the organization, project, and environment before creating the invitation.
- 02
Choose a job-based role
Use a reviewer or developer role when that is sufficient. Reserve owner access for workspace ownership.
- 03
Send the invitation
Invite the teammate using their work email and confirm the pending invitation appears in the same workspace.
- 04
Review access after acceptance
Confirm the teammate can complete the intended task and does not have unrelated access.
What success looks like
- The invitation names the intended workspace and role.
- The teammate signs in with their own account.
- The workspace owner can remove or change the access later.
If something is blocked
- If the wrong workspace is selected, cancel the invitation and create a new one from the intended workspace.
- If the teammate needs another task, change the role deliberately instead of sharing a credential.