You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/docs/administration/access-identity/rbac/scopes/environments.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,6 @@ Note that creating, listing, or restoring environments are organization-level op
25
25
| Value | Description |
26
26
|-------|-------------|
27
27
|`environment:clone`| Create a copy of an existing environment with all its configurations. This is useful for creating staging or testing environments.<br><br>**Granted by default permission**: `Environment Open`|
28
-
|`environment:read_decrypt`| Access and decrypt sensitive environment data. This allows viewing encrypted configuration values and secrets.<br><br>**Granted by default permission**: `Environment Open`|
29
28
|`environment:delete`| Remove an environment and its associated resources. This permanently deletes the environment and its configurations.<br><br>**Granted by default permission**: `Environment Admin`|
30
29
|`environment:open`| Access and interact with an environment's resources. This includes the ability to view and modify environment configurations.<br><br>**Granted by default permission**: `Environment Open`|
31
30
|`environment:read`| View environment configurations and settings. This provides read-only access to environment details and parameters.<br><br>**Granted by default permission**: `Environment Read`|
@@ -63,7 +62,6 @@ Note that creating, listing, or restoring environments are organization-level op
63
62
| Value | Description |
64
63
|-------|-------------|
65
64
|`environment_version:create`| Create a new version of an environment. This allows tracking changes and maintaining environment history.<br><br>**Granted by default permission**: `Environment Write`|
66
-
|`environment_version:read_decrypt`| Access and decrypt sensitive data in an environment version. This allows viewing encrypted configuration values.<br><br>**Granted by default permission**: `Environment Open`|
67
65
|`environment_version:delete`| Remove a specific version of an environment. This permanently deletes the version and its configurations.<br><br>**Granted by default permission**: `Environment Write`|
68
66
|`environment_version:open`| Access and interact with a specific environment version. This includes viewing and using version-specific configurations.<br><br>**Granted by default permission**: `Environment Open`|
69
67
|`environment_version:read`| View details of a specific environment version. This provides access to version-specific configurations and metadata.<br><br>**Granted by default permission**: `Environment Open`|
Copy file name to clipboardExpand all lines: content/docs/administration/access-identity/rbac/scopes/org-settings.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,9 +93,7 @@ This document defines all the available scopes in Pulumi Cloud, organized by [en
93
93
|`org_member:read`| View details about organization members. This includes access to user profiles and roles.<br><br>**Granted by default roles**: `Member`, `Admin`, `Billing Manager`|
94
94
|`org_member:set_admin`| Grant or revoke admin privileges for an organization member. This controls elevated access.<br><br>**Granted by default roles**: `Admin`|
95
95
|`org_member:update`| Update organization member information and roles. This allows changing user details and permissions.<br><br>**Granted by default roles**: `Admin`|
96
-
|`org_requests:create`| Submit a new request to join or interact with the organization. This is used for onboarding or special access. |
97
96
|`org_requests:read`| View all organization requests. This provides visibility into pending and processed requests.<br><br>**Granted by default roles**: `Admin`|
98
-
|`org_requests:status`| Check the status of an organization request. This helps track onboarding or access progress. |
99
97
|`org_requests:update`| Update or process organization requests. This allows approving or denying requests.<br><br>**Granted by default roles**: `Admin`|
100
98
|`invites:create`| Send invitations to new users to join the organization. This enables onboarding of new team members.<br><br>**Granted by default roles**: `Admin`|
101
99
|`invites:read`| View pending and sent invitations for organization membership. This provides visibility into user onboarding status.<br><br>**Granted by default roles**: `Admin`|
@@ -119,8 +117,6 @@ This document defines all the available scopes in Pulumi Cloud, organized by [en
119
117
|`organization:billing`| Manage billing settings and payment methods for the organization. This includes access to invoices and payment history.<br><br>**Granted by default roles**: `Admin`, `Billing Manager`|
120
118
|`organization:change_backend`| Change the backend infrastructure for the organization. This is used for advanced configuration and migration.<br><br>**Granted by default roles**: `Admin`|
121
119
|`organization:delete`| Delete the organization and all its resources. This is a permanent and irreversible action.<br><br>**Granted by default roles**: `Admin`|
122
-
|`organization:read`| View organization details and settings. This includes access to organizational metadata and configuration.<br><br>**Granted by default roles**: `Member`, `Admin`, `Billing Manager`|
123
-
|`organization:read_activity`| View recent activity and audit logs for the organization. This provides insight into changes and events.<br><br>**Granted by default roles**: `Member`, `Admin`, `Billing Manager`|
124
120
|`organization:read_usage`| View usage statistics and metrics for the organization. This includes resource consumption and cost data.<br><br>**Granted by default roles**: `Member`, `Admin`, `Billing Manager`|
125
121
|`organization:rename`| Change the name of the organization. This updates the organization's display name across the platform.<br><br>**Granted by default roles**: `Admin`|
126
122
|`organization:transfer_stacks`| Transfer ownership of stacks between organizations. This is used for organizational restructuring or migration.<br><br>**Granted by default roles**: `Admin`|
0 commit comments