|
7 | 7 | paragraph: Understand the fundamental concepts of Identity and Access Management in Scaleway. |
8 | 8 | tags: advanced settings owner iam principal |
9 | 9 | dates: |
10 | | - validation: 2025-04-08 |
| 10 | + validation: 2025-04-23 |
11 | 11 | --- |
12 | 12 |
|
13 | 13 | <Lightbox src="scaleway-iam-concepts.webp" alt="" /> |
@@ -74,9 +74,9 @@ As a Member you are subject to [complying with the security requirements](/iam/h |
74 | 74 |
|
75 | 75 | ## Organization |
76 | 76 |
|
77 | | -An Organization is made of one or several [Projects](#project). When you create your Scaleway account, an Organization is automatically created, of which you are the Owner. When you create [IAM rules](#rule), you can set their scope at Organization level. |
| 77 | +An Organization is made of one or several [Projects](#project). When you create your Scaleway account, an Organization is automatically created, of which you are the Owner. You can also be added to an existing Organization as a [Guest](#guest) or as a [Member](#member). |
78 | 78 |
|
79 | | -This means you can give access to features managed at Organization level, like billing and IAM, to users, applications, and groups in your Organization. |
| 79 | +When you create [IAM rules](#rule), you can set their scope at Organization level. This means you can give access to features managed at Organization level, like billing and IAM, to users, applications, and groups in your Organization. |
80 | 80 |
|
81 | 81 | <Lightbox src="scaleway-iam-organization.webp" alt="" /> |
82 | 82 |
|
@@ -136,14 +136,7 @@ A rule (also known as an IAM rule) is the part of a [policy](#policy) that defin |
136 | 136 | - **Projects** group your Scaleway resources (e.g. Instances, Object Storage buckets, Managed Databases etc.) together. An Organization may have many Projects, or just one default Project. If you choose to define scope at Project level, you can select one, many, or all Projects. When you then define the [permission sets](#permission-set) for this scope, you can give access to different resources within the Project(s). |
137 | 137 | - An **Organization** is made of one or several Projects. Billing, IAM, Project management and support are all managed at Organization level, so choose the Organization scope to give access to these features. |
138 | 138 | 2. One or more [**permission sets**](#permission-set) (e.g. "list all Instances"). A permission set consists of one or multiple [permissions](#permission) to perform actions on resources or features. Each permission set has a clear description, e.g. `InstancesFullAccess`, `InstancesReadOnly`, `DatabaseFullAccess`, `BillingReadOnly`. |
139 | | - |
140 | | - The rule below defines various levels of access to different resources in Project A. The [principal](#principal) (user, group, or application) can create, list, delete and manage Instances and Databases, but for Object Storage can only list and read the resources: |
141 | | - |
142 | | -SCOPE |
143 | | -: Project A |
144 | | - |
145 | | -PERMISSION SET |
146 | | -: InstancesFullAccess, ObjectStorageReadOnly, DatabasesFullAccess |
| 139 | +3. (Optional) One or more [IAM conditions](#conditions) - defined in Common Expression Language (CEL) expressions. |
147 | 140 |
|
148 | 141 | ## Scope |
149 | 142 |
|
|
0 commit comments