diff options
| author | Chris Akritidis <43294513+cakrit@users.noreply.github.com> | 2023-02-14 09:07:00 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-02-14 09:07:00 -0800 |
| commit | 960f8da6634c58636139bbc77c00d51dbe6ed0d3 (patch) | |
| tree | 462bb67e56b73fcbcb47162f33f0e53ce74b91e0 | |
| parent | 32baa46cb12a157440a325ec72498f2327b4ef45 (diff) | |
Update role-based-access.md (#14528)
| -rw-r--r-- | docs/cloud/manage/role-based-access.md | 9 |
1 files changed, 1 insertions, 8 deletions
diff --git a/docs/cloud/manage/role-based-access.md b/docs/cloud/manage/role-based-access.md index ceee008de6..b6073b0aec 100644 --- a/docs/cloud/manage/role-based-access.md +++ b/docs/cloud/manage/role-based-access.md @@ -26,14 +26,7 @@ being able to join any room. We also aligned the offered roles to the target aud #### What happens to the previous Member role? -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: -* Any new users you invite on the COMMUNITY plan, must be Administrators -* The role Member is deprecated and won’t be selectable in any of the plans -* 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 - -Summary: -* 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. -* 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. +We will maintain a Legacy Community plan for existing users, which will continue to provide access to the Member role. #### Which functionalities are available for each role? |