diff --git a/pages/iam/how-to/manage-groups.mdx b/pages/iam/how-to/manage-groups.mdx index 2317711ee7..8418ae214d 100644 --- a/pages/iam/how-to/manage-groups.mdx +++ b/pages/iam/how-to/manage-groups.mdx @@ -45,14 +45,20 @@ From the groups's [Overview page](#how-to-access-the-group-overview), scroll dow 2. Select the user you want to add from the drop-down menu, or type the name of the user. 3. Click **Validate**. You are returned to the group's overview page, where the newly-added user now appears. + + Keep in mind that, due to replication and caching, any new configuration of permission sets may take up to 1 minute to apply. + + ### Remove users from a group 1. In the **Users** panel, click the **X** button next to the user you want to remove from the group. A pop-up displays asking you to confirm the action. 2. Click **Remove from group** to confirm. - Removing a user from a group means that any permissions given to them via the group (i.e. from an attached policy) will no longer apply. Be sure you want to remove these permissions from the user before proceeding. + - Removing a user from a group means that any permissions given to them via the group (i.e. from an attached policy) will no longer apply. Be sure you want to remove these permissions from the user before proceeding. + - Due to replication and caching, any new configuration of permission sets may take up to 1 minute to apply. + ## How to manage a group's applications From the group's [Overview page](#how-to-access-the-group-overview), scroll to the **Applications** panel. A list of all applications in the group displays. @@ -80,7 +86,8 @@ From the groups' [Overview page](#how-to-access-the-group-overview), scroll to t 1. In the **Policies** panel, click the **X** button next to the policy you want to detach from the group. A pop-up displays asking you to confirm the action. 2. Click **Detach policy** to confirm. - Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + - Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + - Due to replication and caching, any new configuration of permission sets may take up to 1 minute to apply. ### Attach a policy to a group @@ -96,6 +103,10 @@ A group may be attached to multiple policies. To create a new policy, see our [dedicated how to](/iam/how-to/create-policy/). + + Keep in mind that, due to replication and caching, any new configuration of permission sets may take up to 1 minute to apply. + + ## How to delete a group 1. From the groups's [**Overview** tab](#how-to-access-the-group-overview), scroll down to the **Delete group** panel. diff --git a/pages/iam/how-to/manage-policies.mdx b/pages/iam/how-to/manage-policies.mdx index 51f0e3c9de..4e7de5af9a 100644 --- a/pages/iam/how-to/manage-policies.mdx +++ b/pages/iam/how-to/manage-policies.mdx @@ -42,7 +42,9 @@ From the policy's [Overview page](#how-to-access-the-policy-overview): 1. From the policy's [Overview page](#how-to-access-the-policy-overview), scroll down to the **Rules** panel and click next to the rule you want to edit. 2. Edit the rule as required. You can edit the scope, permission sets and conditions. - Conditions can only be edited using the **Advanced** editor. You must update the [CEL](/iam/concepts#common-expression-language-cel) expression in the editor to update the condition. Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for more details about how to write condition expressions, as well as examples of conditions. + Keep in mind that: + - Conditions can only be edited using the **Advanced** editor. You must update the [CEL](/iam/concepts#common-expression-language-cel) expression in the editor to update the condition. Refer to the [Understanding policy conditions](/iam/reference-content/understanding-policy-conditions) documentation page for more details about how to write condition expressions, as well as examples of conditions. + - Due to replication and caching, whenever you update a policy, any new configuration of permission sets may take up to 1 minute to apply. 3. Click **Validate** to finish. @@ -54,7 +56,8 @@ From the policy's [Overview page](#how-to-access-the-policy-overview): 1. Click the **x** button next to the policy you want to detach from the user. A pop-up displays asking you to confirm the action. 2. Click **Detach policy** to confirm. - Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the user means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + - Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the user means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + - Due to replication and caching, whenever you update a policy, any new configuration of permission sets may take up to 1 minute to apply. ## How to attach another policy to a user @@ -71,6 +74,10 @@ A user may be attached to multiple policies. 4. Click **Validate** to finish. The selected policy is attached to the user. + + Keep in mind that, due to replication and caching, whenever you update a policy, any new configuration of permission sets may take up to 1 minute to apply. + + ## How to delete a policy @@ -81,4 +88,6 @@ A user may be attached to multiple policies. 2. Click **Delete policy**. A warning displays, asking you to confirm your action. 3. Type **DELETE** to confirm, and click **Delete policy** to validate. - + + Keep in mind that, due to replication and caching, whenever you update a policy, any new configuration of permission sets may take up to 1 minute to apply. + diff --git a/pages/iam/reference-content/policy.mdx b/pages/iam/reference-content/policy.mdx index fdac9c2401..fa5a55b59b 100644 --- a/pages/iam/reference-content/policy.mdx +++ b/pages/iam/reference-content/policy.mdx @@ -49,6 +49,10 @@ A permission set consists of one or multiple permissions to perform actions on r You can find a detailed list of all permission sets available at Scaleway in the permission sets [reference page](/iam/reference-content/permission-sets/). + + Keep in mind that, due to replication and caching, any new configuration of permission sets may take up to 1 minute to apply. + + ### Conditions A condition is an additional layer of restrictions for your rule. You can allow access to specific user agents or IP addresses, and allow actions to be performed only at certain dates and times. Conditions are defined through [CEL](#common-expression-language-cel) expressions. In general, a condition expression consists of one or more statements that are joined by logical operators (`&&`, `||`, or `!`).