Teams

What a team is for

A team provides a shared collaboration space. It makes it easier to share resources, models, tools, and API access within a common scope.

What can be managed

Within a team, it is possible to:

• create and administer the team
• invite members
• assign roles
• review the member list
• access shared resources
• adjust team-related settings

Invitations

Invitations are used to add new members. Depending on the current context, some actions can depend on the status of the subscription.

Roles

The visible role labels in the product are:

• Owner
• Administrator
• Member

The least permissive role that still fits the need is usually the right choice.

Active team

Some sections, such as API Tokens and Subscription, rely on the active team. If a screen does not show the expected content, the active team is often the key setting to verify.

When to create multiple teams

Creating several teams is useful when:

• sharing boundaries differ
• access rules need to stay isolated
• subscriptions or budgets should be separated

Good practices

• Keep governance simple.
• clean up outdated invitations
• avoid using one team for every use case when access rules should differ