TempsTemps
On this page
  1. Inviting team members
  2. Roles
  3. Removing members
  4. Audit log
  5. SSO

Teams & Collaboration

Temps includes unlimited seats — invite your entire team at no extra cost. Access is controlled by roles at the organization and project level.

Inviting team members

Add a team member

  1. 1

    Go to Settings, then Team, then click Invite Member.

  2. 2

    Enter the email address and choose a role.

  3. 3

    Send the invite. The invitee receives an email link valid for 48 hours.

    Checkpoint: Once they accept, confirm they appear in the member list under Settings, then Team.

  1. Go to Settings → Team → Invite Member
  2. Enter the email address and choose a role
  3. The invitee receives an email link valid for 48 hours
  4. Once accepted, they appear in the member list

Pending invitations can be revoked from Settings → Team → Pending Invites.

Roles

RoleDescription
OwnerFull access — billing, all projects
AdminAll project access (not billing)
DeployerDeploy, view logs, manage environment variables
ViewerRead-only access to projects and logs

Team creation and membership management require the instance-wide Admin role, independent of the team or project role a member holds.

These are the roles a member can hold within a team. A team's role determines what its members can do on the projects that team has access to.

Project-level access

Grant a team access to a project

  1. 1

    Open the project and go to Settings, then Access.

  2. 2

    Click Grant access.

  3. 3

    Select a team and the role that team holds on this project, then save.

    Checkpoint: Confirm the team and role are listed on the project Access page.

Project access in Temps is granted to teams, not individual users. Grant a team a role on a specific project:

  1. Go to Project → Settings → Access
  2. Click Grant access
  3. Select a team (not a user) and the role that team holds on this project

A member's effective permission on a project is the intersection of their role within the team and the role that team holds on the project — there is no per-user project-role override.

Removing members

Remove a team member

  1. 1

    Go to Settings, then Team.

  2. 2

    Find the member you want to remove.

  3. 3

    Click Remove.

    Checkpoint: Their sessions are invalidated immediately; confirm they no longer appear in the member list.

Go to Settings → Team, find the member, and click Remove. Their sessions are invalidated immediately. Projects they deployed remain untouched.

Audit log

Every action that changes state — deploys, environment variable edits, domain changes, team changes — is recorded in the audit log.

Settings → Audit Log shows:

  • Who performed the action
  • What changed (before/after for variable edits)
  • When it happened (UTC timestamp)
  • Which project or resource was affected

The audit log is append-only and cannot be edited or deleted.

# Export audit log
bunx @temps-sdk/cli audit list --from 2026-01-01 --to 2026-12-31 --json > audit-export.json

SSO

Enable SSO (OIDC)

  1. 1

    Go to Settings, then Security, then SSO.

  2. 2

    Configure your identity provider with the OIDC details.

  3. 3

    Enable SSO. Once enabled, password and OAuth login are disabled for SSO-enrolled users.

    Checkpoint: SSO enforcement does not affect the owner account until the owner explicitly enables it for themselves, which prevents accidental lockout during setup.

Temps supports SSO via OpenID Connect (OIDC). Configure your identity provider under Settings → Security → SSO — see OIDC Single Sign-On for the full setup guide. Once enabled, all team members must authenticate through the IdP — password and OAuth login are disabled for SSO-enrolled users.

SSO enforcement does not affect the owner account until the owner explicitly enables it. This prevents accidental lockout during setup.

Was this page helpful?