Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
admin:managing_users [2025/01/06 17:53] – [Buttons on the Permissions tabs] Gary Willetts | admin:managing_users [2025/07/28 08:29] (current) – [Active] Mark Glover | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== 25.15. Managing users ====== | ====== 25.15. Managing users ====== | ||
===== About users and groups ===== | ===== About users and groups ===== | ||
+ | mSupply has a comprehensive system of controlling user access, allowing you to manage in fine detail what each user can do and see in the system. You can manage users individually, | ||
+ | |||
User permissions are per-store, so a user can have different permissions when logged into different stores. | User permissions are per-store, so a user can have different permissions when logged into different stores. | ||
- | If you have many users that need to have the same permissions (because they carry out the same role, for example), | + | If you have many users that need to have the same permissions (because they carry out the same role, for example), |
- | <WRAP center round tip 95%> | + | ==== Users and sync ==== |
- | If you want to change | + | A few points |
- | * Edit the user, change | + | * Users are // |
- | * Open the user again and their permissions will be editable. | + | * // |
- | Refer to [[admin: | + | * Users can be created and edited on a Legacy mSupply remote site. Name details of any newly created user on a remote site will sync back to the Legacy mSupply Central server. |
- | </WRAP> | + | * As of 2025-07-28, users can not be created or permissions |
- | <WRAP center round important 95%> | ||
- | If you want to disable a user, perhaps because the staff member has left the organisation, | ||
- | * Edit the user, uncheck the **Active** checkbox, click **OK**. | ||
- | |||
- | If the **Active** checkbox is greyed out, it is because they are a member of a group. You will need to first remove them from the group before you can make them ' | ||
- | * Edit the user, change the **Is a member of** to '' | ||
- | * Edit the user, uncheck the **Active** checkbox, click **OK**. | ||
- | |||
- | Of course, if the whole group of users needs to be made inactive then you can just uncheck the **Active** checkbox for the group. | ||
- | </ | ||
===== Adding and editing users and groups ===== | ===== Adding and editing users and groups ===== | ||
- | mSupply has a comprehensive system of controlling user access, allowing you to manage in fine detail what each user can do and see in the system. You can manage users individually, | ||
User access is managed by choosing **File > Edit users** from the menus, or by choosing **Admin > Edit users** in the Navigator. When clicking on this option you are presented with a list of current users: | User access is managed by choosing **File > Edit users** from the menus, or by choosing **Admin > Edit users** in the Navigator. When clicking on this option you are presented with a list of current users: | ||
Line 52: | Line 43: | ||
===== User details window ===== | ===== User details window ===== | ||
+ | <WRAP center round tip 95%> | ||
+ | If you want to change a user's permissions and find out that all their permissions are greyed out and uneditable then it means they are a member of a group. To edit their permissions separately from the group, they must first be removed from the group: | ||
+ | * Edit the user, change the **Is a member of** drop down list to '' | ||
+ | * Open the user again and their permissions will be editable. | ||
+ | Refer to [[admin: | ||
+ | </ | ||
{{ : | {{ : | ||
Line 68: | Line 65: | ||
=== Active === | === Active === | ||
If this checkbox is checked, then that user has permission to use the system, and their name will appear in the login window. If this checkbox is unchecked the user will not be allowed to login to the system and their name will not appear in the login window. | If this checkbox is checked, then that user has permission to use the system, and their name will appear in the login window. If this checkbox is unchecked the user will not be allowed to login to the system and their name will not appear in the login window. | ||
+ | <WRAP center round important 95%> | ||
+ | If you want to disable a user, perhaps because the staff member has left the organisation, | ||
+ | * Edit the user, uncheck the **Active** checkbox, click **OK**. | ||
+ | |||
+ | If the **Active** checkbox is greyed out, it is because they are a member of a group. You will need to first remove them from the group before you can make them ' | ||
+ | * Edit the user, change the **Is a member of** to '' | ||
+ | * Edit the user, uncheck the **Active** checkbox, click **OK**. | ||
+ | |||
+ | Of course, if the whole group of users needs to be made inactive then you can just uncheck the **Active** checkbox for the group. | ||
+ | </ | ||
=== Can be responsible officer === | === Can be responsible officer === | ||
Line 123: | Line 130: | ||
=== Buttons on the Permissions tabs === | === Buttons on the Permissions tabs === | ||
- | | + | == Store == |
+ | |||
+ | The **Store** drop down list allows you to select | ||
You can type in the drop down list. If you do this, when you click on the down arrow to open it, you will only be shown stores in the list which start with what you typed. Or, if you prefix it with the mSupply wildcard character, " | You can type in the drop down list. If you do this, when you click on the down arrow to open it, you will only be shown stores in the list which start with what you typed. Or, if you prefix it with the mSupply wildcard character, " | ||
- | </ | + | </ |
- | | + | |
- | * The **Copy** button: Copies the state of all the checkboxes on the tab for this store to an internal clipboard for that tab. From version 5.03 onwards, the button opens this window:{{ : | + | == All on == |
- | * In the // | + | The **All on** button |
- | * In the table, select the stores you want to copy the permissions of the current store to by checking them in the // | + | |
- | * Click the **OK** button to copy the selected permissions tabs of the current store to the selected stores. Click the **Cancel** button to close the window without doing anything. | + | == Copy == |
- | * The **Paste** button: Only exists | + | The **Copy** button |
+ | - In the // | ||
+ | - In the table, select the stores you want to paste the permissions of the current | ||
+ | - Click the **OK** button to copy the selected permissions | ||
+ | === Permissions === | ||
Most of the permissions are self explanatory. Those that need more explanation are given below: | Most of the permissions are self explanatory. Those that need more explanation are given below: | ||
Line 260: | Line 273: | ||
Note that you won't be able to delete a group that has users belonging to it. If you really want to delete the group, remove all users from the group first by editing their //Is a member of// fields. | Note that you won't be able to delete a group that has users belonging to it. If you really want to delete the group, remove all users from the group first by editing their //Is a member of// fields. | ||
- | ===== Managing and using groups ===== | + | ===== User groups ===== |
mSupply allows for a high granularity of user permission configuration. | mSupply allows for a high granularity of user permission configuration. | ||
Line 271: | Line 284: | ||
<WRAP center round important 60%> | <WRAP center round important 60%> | ||
- | A user can have permission to view or edit data while logged in to a particular store, either directly or through membership of a group. | + | A user can have permission to view or edit data while logged in to a particular store, either directly or through membership of a group. |
+ | This can be very helpful if you have a common set of permissions that you want a class of users to have, and this class of user exists in hundreds of stores. | ||
+ | - Log in to one store and configure an **OIC** group with all the necessary OIC permissions | ||
+ | - [[admin: | ||
+ | - Create an OIC user for each store, make them a member of the **OIC** group | ||
+ | - Configure them to be able to have [[admin: | ||
</ | </ | ||