Skip to content

Commit 7ddb535

Browse files
fix(iam): bye bye guests
1 parent 9bbe26d commit 7ddb535

File tree

5 files changed

+6
-28
lines changed

5 files changed

+6
-28
lines changed

pages/account/how-to/manage-notifications.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The **notification manager** allows you to configure different types of notifica
2626
2. Scroll to the **User notifications** section.
2727
3. Check the box(es) next to the email of the user for who you want to set up the notifications. Four [types of notifications](#types-of-notifications) are available: **Incident**, **Technical**, **Security** and **Billing**.
2828
<Message type="important">
29-
The emails displayed in the list belong to users in your Organization. To see them in the list, first you must have either [invited them as a Guest](/iam/how-to/invite-user-to-orga/), or [created a new Member](/iam/how-to/manage-members/#how-to-create-a-member).
29+
The emails displayed in the list belong to users in your Organization. To see them in the list, first you must [created a new Member](/iam/how-to/manage-members/#how-to-create-a-member).
3030
</Message>
3131

3232
When you check the box, the user is automatically subscribed to the notifications.

pages/billing/how-to/add-billing-contact.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,9 @@ When you enable billing notifications for a user they will receive your Organiza
2424

2525
## How to set up notifications for internal users
2626

27-
1. Add the intended billing contact as an IAM user. You can:
28-
- [Invite them as a Guest](/iam/how-to/invite-user-to-orga/), or
29-
- [Create a new Member](/iam/how-to/manage-members/#how-to-create-a-member).
30-
2. Follow the steps described in the "How to notify users in your Organization" section of the [How to manage notifications](/account/how-to/manage-notifications/#how-to-notify-users-in-your-organization) documentation page.
27+
1. Add the intended billing contact as an IAM user.
28+
2. [Create a new Member](/iam/how-to/manage-members/#how-to-create-a-member).
29+
3. Follow the steps described in the "How to notify users in your Organization" section of the [How to manage notifications](/account/how-to/manage-notifications/#how-to-notify-users-in-your-organization) documentation page.
3130

3231
## How to set up notifications for external users
3332

pages/iam/concepts.mdx

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -48,14 +48,6 @@ The grace period is the time an [IAM Member](#members) has to comply with the se
4848

4949
A group (also known as an IAM group) is a grouping of [users](#user) and/or [applications](#application). Creating groups allows you to attach [policies](#policy) to multiple users and/or applications at the same time.
5050

51-
## Guest
52-
53-
You are the [Owner](#owner) of the Organization that is created with your Scaleway account. However, when you are invited to another Organization of which you are not the Owner, you are a **Guest** in that Organization.
54-
55-
<Message type="important">
56-
Guests will be deprecated by July 2025. From then on, only Members can be created as users of your Organizations, and adding Guests to an Organization will no longer be possible.
57-
</Message>
58-
5951
## IAM
6052

6153
**I**dentity and **A**ccess **M**anagement allows you to share access to the management of your Scaleway [resources](#resource) in a controlled and secure manner.
@@ -157,10 +149,6 @@ Keep in mind that:
157149

158150
A user (also known as an IAM user) is a human user in an Organization. They can be of two types:
159151
- **Owner**: You are the Owner of the [Organization](#organization) that was created with your account.
160-
- **Guest**: You are a Guest when invited to another Organization of which you are not the Owner.
161-
<Message type="important">
162-
Guests will be deprecated by July 2025. From then on, only Members can be created as users of your Organizations.
163-
</Message>
164152
- **Member**: You are a Member when you are added to an Organization by an Owner or user with IAM Manager permissions. Members exist only within the specific Organizations in which they are created.
165153

166154
Within each Organization, different IAM users can have different rights (defined through [policies](#policy)) to perform actions on resources.

pages/organizations-and-projects/concepts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Each [Organization](#organization) has at least one associated [Project](#projec
1818

1919
## Organization
2020

21-
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).
21+
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 [Member](#member).
2222

2323
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.
2424

pages/organizations-and-projects/how-to/enforce-mfa.mdx

Lines changed: 1 addition & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -28,21 +28,12 @@ categories:
2828
5. Type **ENFORCE** in the box.
2929
<Message type="important">
3030
Keep in mind that:
31-
- MFA will become mandatory for all users in the Organization. When you invite [Guests](/iam/concepts/#guest) to your Organization in the future, they must have set up MFA to be able to join. <br /><br />
32-
- You can only enforce MFA if all Guests in your Organization have already set up MFA on their accounts.
31+
- MFA will become mandatory for all users in the Organization.<br /><br />
3332
- If MFA is enforced in your Organization, all new [Members](/iam/concepts/#member) you create will have to enable MFA within the [grace period](/iam/concepts/#grace-period) you set. If they fail to do so before the grace period is over, their account will be locked. The same applies for existing members who do not yet have MFA enabled. Once you enforce MFA, they also have to comply with this [security requirement](/iam/how-to/enforce-security-requirements-members) within the grace period.
3433
</Message>
3534
6. Click **Enforce MFA**.
3635
- If all users in your Organization already have enabled MFA, a confirmation message appears on the top right corner of the screen.
3736

38-
- If at least one of the Guests does not have MFA enabled, you must send them an [MFA reminder](#how-to-send-an-mfa-reminder).
39-
40-
## How to send an MFA reminder
41-
42-
1. Click **IAM & API keys** on the top-right drop-down menu of the Scaleway console. The **Users** tab displays.
43-
2. Click <Icon name="more" /> > **Send MFA reminder** next to the name of a user that has MFA disabled.
44-
The user will receive an email requesting that they enable MFA.
45-
4637
## How to stop enforcing MFA
4738

4839
<Message type="requirement">

0 commit comments

Comments
 (0)