Skip to content

Commit e824cce

Browse files
fix(iam): add procedure
1 parent be098ba commit e824cce

File tree

1 file changed

+36
-14
lines changed

1 file changed

+36
-14
lines changed

pages/iam/reference-content/guests-to-members-migration.mdx

Lines changed: 36 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,25 @@ Whereas Owners have full rights and access to all resources and features in thei
2727

2828
From June 2025, IAM Guests will become IAM Members. The migration process will be carried out in two phases:
2929

30-
- **Phase 1** - Starting on the *18th of July 2025*, the [manual migration of Guests]() will be available in the Console to all Owners and users with [IAMManager permissions](/iam/reference-content/permission-sets) until
30+
- **Phase 1** - Starting on the *18th of July 2025*, the [manual migration of Guests](#how-to-manually-migrate-a-user-from-guest-to-member) will be available in the Console to all Owners and users with [IAMManager permissions](/iam/reference-content/permission-sets).
3131
- **Phase 2** - Starting in *July 2025*, Guests that have not yet become members will be automatically migrated.
3232

33+
Keep in mind that:
34+
35+
- Members exist only within the Organizations in which they were created, and have a [dedicated login process](/iam/how-to/log-in-as-a-member).
36+
- Organization admins manage Member accounts, including enforcing security requirements (MFA, password renewal).
37+
- Single Sign-On (SSO) remains available.
38+
- The management of API keys, IAM policies, and groups remains the same.
39+
40+
### What remains the same?
41+
42+
| Feature | for Members |
43+
|:--------:|----------|
44+
| Single Sign-On (SSO) | Available |
45+
| Credentials (Password, SSO, MFA) | Members who previously existed as Guests maintain the same credentials configuration as before. |
46+
| Access control | Like Guests, Members are granted permissions to the Organization by way of IAM policies. |
47+
| API keys | The processes for creating, viewing and deleting API keys remain the same. |
48+
3349
### What changes?
3450

3551
The table below summarizes the key account and access management features that Scaleway offered prior to IAM, and if/how they change with the introduction of Members. For more information, see the relevant sections of this document below.
@@ -42,22 +58,28 @@ The table below summarizes the key account and access management features that S
4258
| User management | Guest accounts and personal Organizations could not be managed by anyone other than them. Their permissions on Organizations they were invited to are the prerogative of Organization admins. | Member accounts are an 100% manageable resource - they can be created, updated, locked and deleted by Organization admins. |
4359
| Organizations | Guests were users who had their own personal Organizations and were invited into another. They had full management rights on their accounts and Organizations. If they were removed from an Organization, they would continue to have a Scaleway account. | Members exist only within an Organization and can be present in solely said Organization. Members cannot own Organizations. They must [comply to the security requirements](/iam/how-to/comply-with-sec-requirements-member) set for the Organization to ensure their continuous access. |
4460

45-
46-
### What remains the same?
47-
48-
| Feature | Guests | Members |
49-
|:--------:|:-------:|----------|
50-
| Single Sign-On (SSO) | Available | Available |
51-
| Credentials (Password, SSO, MFA) | - | Members who previously existed as Guests maintain the same credentials configuration as before. |
52-
| Access control | - | Like Guests, Members are granted permissions to the Organization by way of IAM policies. |
53-
| API keys | - | The processes for creating, viewing and deleting API keys remain the same. |
54-
55-
5661
## How to manually migrate a user from Guest to Member
5762

5863
<Message type="important">
5964
The migration does not effect any impacts to your production.
6065
</Message>
6166

62-
63-
67+
<Macro id="requirements" />
68+
69+
- A Scaleway account logged into the [console](https://console.scaleway.com)
70+
- [Owner](/iam/concepts/#owner) status or [IAMManager permissions](/iam/concepts/#permission)
71+
72+
1. Click **IAM & API keys** on the top-right drop-down menu of the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays.
73+
2. Click **Switch to Members** in the *Switch to IAM Members* top banner. A pop-up appears providing information about Member features.
74+
3. Click **Next**. More information about the changes for your users displays.
75+
4. Click **Next** again.
76+
5. Type **MIGRATE**.
77+
<Message type="important">
78+
Make sure you are sure of migrating before continuing. Switching to Members is a one-time irreversible action.
79+
</Message>
80+
6. Click **Migrate**.
81+
<Message type="note">
82+
The migration might take up to one minute.
83+
</Message>
84+
85+
You receive an email to confirm the migration. The former Guests, now Members, also receive an email with their credentials instructions on how to log in as a member for the first time.

0 commit comments

Comments
 (0)