For the complete documentation index, see llms.txt. This page is also available as Markdown.

Team Management

Invite Teammates, assign roles by scope, and keep access aligned to delivery needs.

Overview

Team Management controls who can access Transform. It also controls what actions are permitted. Access is scoped to Account, Organization, and Project.

Key Concepts

  • Teammate: person record with access at one or more scopes

  • Scope: what a Teammate can see (Account, Organization, Project)

  • Role: what a Teammate can do within a scope

  • Least privilege: grant only the access required for delivery work

How It’s Used

Use this section during onboarding and governance changes. Use it for regular access reviews and offboarding.

Benefits

  • Reduced risk from over-scoped access

  • Cleaner collaboration through consistent role assignment

  • Easier audits through predictable access patterns

Setup Steps

1

Define access scope

Start by picking scope, then assign a role.

2

Invite or update Teammates

3

Standardize roles and permissions

Best Practices

  • Limit Account Admin and Owner roles to a small set.

  • Prefer Project scope for external collaborators.

  • Review access monthly and after major delivery milestones.

Summary

Team Management is the control plane for access and collaboration. Scope controls visibility. Roles control actions.

Last updated