added section to explain impacts on member role (#14527)
Hugo Valente committed
Feb 14, 2023 at 15:37 UTC
639ca97330cec016e7345d03fb5736f5f13d8058
1 file changed
+11
docs/cloud/manage/role-based-access.md
+11
@@ -24,6 +24,17 @@ being able to join any room. We also aligned the offered roles to the target aud
24
| **Observers**<p>This role is for read-only access with restricted access to explicit War Rooms and only the Nodes that appear in those War Rooms.</p>💡 Ideal for restricting your customer's access to their own dedicated rooms.<p></p> | - | - | :heavy_check_mark: |
25
| **Billing**<p>This role is for users that need to manage billing options and see invoices, with no further access to the system.</p> | - | - | :heavy_check_mark: |
26
27
+#### What happens to the previous Member role?
28
+
29
+We don't want to disrupt your current access rights. Users that currently have the legacy Member role, will not lose their access, or permissions. The impact is:
30
+* Any new users you invite on the COMMUNITY plan, must be Administrators
31
+* The role Member is deprecated and won’t be selectable in any of the plans
32
+* Current Members will not be able to invite other users to the space, since they would only be able to invite Members which is deprecated
33
+
34
+Summary:
35
+* If you don’t upgrade, keep your space on Community plan: You don’t need to do anything with your existing users, they will not notice a difference.
36
+* If you do upgrade, move to one of the paid plans: We suggest you reassign your existing Members to one of the new roles, depending on their needs.
37
+
38
#### Which functionalities are available for each role?
39
40
In more detail, you can find on the following tables which functionalities are available for each role on each domain.