1. Docs
2. Reference
3. REST API Docs
4. Schema
5. TeamPermission

TeamPermission describes the team and the stack permission that team has for a specific stack.

Properties

• team Team required
  The team that has been granted access to the stack.
• ↳ kind enum required
  The kind of team (e.g., pulumi or GitHub-backed).
  Values:

  github — GitHub

  TeamKindGitHub is for teams where membership is managed by GitHub.

  pulumi — Pulumi

  TeamKindPulumi is for teams where membership is managed by Pulumi.

  scim — SCIM

  TeamKindSCIM is for SCIM provisioned teams. Membership is managed by its IdP.

• ↳ name string required
  The unique identifier name of the team within the organization.
• ↳ displayName string required
  The human-readable display name shown in the UI.
• ↳ description string required
  A free-form text description of the team’s purpose.
• ↳ members array[TeamMemberInfo] optional
  The list of team members.
• ↳ stacks array[TeamStackPermission] optional
  The list of stack permissions granted to the team.
• ↳ environments array[TeamEnvironmentSettings] optional
  The list of environment settings for the team.
• ↳ accounts array[TeamAccountPermission] optional
  The list of account permissions granted to the team.
• ↳ listMembersError string optional
  ListMembersError is the error message if an error was encountered whilst trying to contact the team’s backend (eg. GitHub). The UI will only show this error if it is non-nil and if Members itself is an empty slice.
• ↳ userRole enum optional
  UserRole is the calling user’s role on the given team.
  Values: none, member, admin
• ↳ roleIds array[string] optional
  RoleIDs are the IDs of the FGA roles assigned to the team, if any. Currently only one role per team is supported.
• permission enum required
  The permission level the team has on the stack (e.g., read, write, admin).
  Values:

  0 — None

  StackPermissionNone provides no access.

  101 — Read

  StackPermissionRead provides read-only access, including the ability to decrypt encrypted configuration secrets stored in the service.

  102 — Write

  StackPermissionWrite provides read/write access to a stack.

  103 — Admin

  StackPermissionAdmin provides admin-level access to the stack. For example, being able to run pulumi destroy or delete the stack.

  104 — Creator

  StackPermissionCreator identifies the user who created the stack. It confers the same access as StackPermissionAdmin.