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

ListMemberStackPermissionsResponse describes all the permissions that have been set for a user for a specific stack.

Properties

• userInfo UserInfo required
  The user information
• ↳ name string required
  The user’s display name.
• ↳ githubLogin string required
  The user’s login name.
• ↳ avatarUrl string required
  The URL of the user’s avatar image.
• ↳ email string optional
  The user’s email address. It is only populated on selected endpoints and is omitted from most responses. Treat it as sensitive information.
• organizationRole enum required
  The user’s role within the organization
  Values:

  none — None

  OrganizationRoleNone describes the role of non-members.

  member — Member

  OrganizationRoleMember is the role for regular members.

  admin — Admin

  OrganizationRoleAdmin is the role for admins.

  potential-member — PotentialMember

  OrganizationRolePotentialMember is the role for users who are explicitly not a member of the organization, but are a member of the backing org on the 3rd party identity provider. (i.e. they could join the org.)

  stack-collaborator — StackCollaborator

  OrganizationRoleStackCollaborator is the role for users who are not a member of an organization, but have been explicitly granted access to some of the organization’s stacks. So they have limited permissions to access the org’s data.

  billing-manager — BillingManager

  OrganizationRoleBillingManager is the role for billing admins.

• organizationDefault enum required
  The organization’s default stack permission level
  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.

• teamPermissions array[TeamPermission] required
  The list of team-based permissions for this stack
• ↳ team Team required
  The team that has been granted access to the stack.
• ↳ 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.

• explicitPermission enum required
  The explicitly assigned permission for this user on this stack
  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.