From bfc1acfda39f61373b8e445bed9965f90c947ec0 Mon Sep 17 00:00:00 2001 From: it33 Date: Thu, 12 Nov 2015 18:43:16 -0800 Subject: Rename doc/help/Manage-Members.md to doc/help/team-settings/Manage-Members.md --- doc/help/Manage-Members.md | 37 -------------------------------- doc/help/team-settings/Manage-Members.md | 37 ++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+), 37 deletions(-) delete mode 100644 doc/help/Manage-Members.md create mode 100644 doc/help/team-settings/Manage-Members.md (limited to 'doc/help') diff --git a/doc/help/Manage-Members.md b/doc/help/Manage-Members.md deleted file mode 100644 index 04243f9fb..000000000 --- a/doc/help/Manage-Members.md +++ /dev/null @@ -1,37 +0,0 @@ -# Manage Members - -The Manage Members menu is used to change the user roles assigned to members belonging to a team. - -## User Roles - -The following user roles are assigned from the **Manage Members** menu option in the team site main menu. - -### System Admin - -The System Administrator is typically a member of the IT staff and has the follow privileges: - -- Access to the System Console from the main menu in any team site. -- Change any setting on the Mattermost server available in the System Console. -- Promote and demote other users to and from the System Admin role. -- This role also has all the privileges of the Team Administrator as described below - -The first user added to a newly installed Mattermost system is assigned the System Admin role. - -### Team Admin - -The Team Administrator is typically a non-technical end user and has the following privileges: - -- Access to the "Team Settings" menu from the team site main menu -- Ability to change the team name and import data from Slack export files -- Access to the "Manage Members" menu and change user roles to the levels of Team Administrator, Member and Inactive - -### Member - -This is the default role given to end users who join the system. Members have basic permissions to use the Mattermost team site. - -### Inactive - -This status is given to users whose accounts are marked inactive. These users can no longer log into the system. - -Because Mattermost is designed as a system-of-record, there is not an option to delete users from the Mattermost system, as such an operation could compromise the integrity of message archives. - diff --git a/doc/help/team-settings/Manage-Members.md b/doc/help/team-settings/Manage-Members.md new file mode 100644 index 000000000..04243f9fb --- /dev/null +++ b/doc/help/team-settings/Manage-Members.md @@ -0,0 +1,37 @@ +# Manage Members + +The Manage Members menu is used to change the user roles assigned to members belonging to a team. + +## User Roles + +The following user roles are assigned from the **Manage Members** menu option in the team site main menu. + +### System Admin + +The System Administrator is typically a member of the IT staff and has the follow privileges: + +- Access to the System Console from the main menu in any team site. +- Change any setting on the Mattermost server available in the System Console. +- Promote and demote other users to and from the System Admin role. +- This role also has all the privileges of the Team Administrator as described below + +The first user added to a newly installed Mattermost system is assigned the System Admin role. + +### Team Admin + +The Team Administrator is typically a non-technical end user and has the following privileges: + +- Access to the "Team Settings" menu from the team site main menu +- Ability to change the team name and import data from Slack export files +- Access to the "Manage Members" menu and change user roles to the levels of Team Administrator, Member and Inactive + +### Member + +This is the default role given to end users who join the system. Members have basic permissions to use the Mattermost team site. + +### Inactive + +This status is given to users whose accounts are marked inactive. These users can no longer log into the system. + +Because Mattermost is designed as a system-of-record, there is not an option to delete users from the Mattermost system, as such an operation could compromise the integrity of message archives. + -- cgit v1.2.3-1-g7c22