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 [2026/05/27 15:07] – [Reports] Gary Willetts | admin:managing_users [2026/09/30 12:56] (current) – [Users and sync] Gary Willetts | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| ==== Users and sync ==== | ==== Users and sync ==== | ||
| A few points to remember if you are working with users on a [[synchronisation: | A few points to remember if you are working with users on a [[synchronisation: | ||
| - | * Users are // | + | * Users are // |
| - | * // | + | * // |
| * 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. | * 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. | ||
| - | * As of 2025-07-28, users can not be created or permissions edited on [[https:// | + | * Users can not be created or permissions edited on [[https:// |
| Line 46: | Line 46: | ||
| * **Permission report:** produces a report which shows all the permissions the selected (highlighted) user or group has in all stores in the datafile. It looks like this:{{ .: | * **Permission report:** produces a report which shows all the permissions the selected (highlighted) user or group has in all stores in the datafile. It looks like this:{{ .: | ||
| * **User stores report:** produces a report which shows all the stores all the users in the datafile can login to. It looks like this:{{ .: | * **User stores report:** produces a report which shows all the stores all the users in the datafile can login to. It looks like this:{{ .: | ||
| + | |||
| + | As soon as you click on one of the options, the report is generated and opened in your spreadsheet application. | ||
| ===== User details window ===== | ===== User details window ===== | ||
| <WRAP center round tip 95%> | <WRAP center round tip 95%> | ||
| Line 240: | Line 242: | ||
| * " | * " | ||
| - | === Sync user across all login stores === | + | === Sync user across all login stores |
| + | This checkbox is only displayed if the user is logged into the primary server in a synchronisation system. | ||
| - | The **Sync user across all login stores** checkbox is only displayed if the user is logged into the primary server in a synchronisation system. | + | If this checkbox is checked, when the **OK** button is clicked |
| - | As you can imagine, **Sync user across all login stores** is a powerful feature, and can have unintended consequences. | + | |
| - | </ | + | |
| + | In this way, an administrator in a synchronisation system is able to edit user permissions and settings centrally and have them automatically synchronised to all relevant sites, rather than having to log in remotely to those sites and configure permissions locally. | ||
| + | |||
| + | As you can imagine, this is a powerful feature and can have unintended consequences so be careful when using it! | ||
| <WRAP center round important 60%> | <WRAP center round important 60%> | ||
| - | **Sync user across all login stores** will propagate: | + | **Sync user across all login stores** will <wrap em> |
| - | * Group permissions | + | |
| - | * User group membership (which group the user is a member of) | + | |
| - | * User permissions, | + | |
| - | * User store login permissions | + | |
| - | + | ||
| - | **Sync user across all login stores** will <wrap em> | + | |
| - | * User deletion | + | |
| - | * Group deletion | + | |
| - | Deleting | + | Deleting |
| - | * Manually | + | |
| - | * Development and execution of custom | + | |
| </ | </ | ||
| Line 389: | Line 383: | ||
| Your own templates are created as user group permission reports which you then load into a user's permissions. To do this, follow these steps: | Your own templates are created as user group permission reports which you then load into a user's permissions. To do this, follow these steps: | ||
| - | - Create a user group which has the permissions you require set on the // | + | - Create a user group which has the permissions you require |
| + | - View the list of user groups (see the [[admin: | ||
| + | - Run a Permission report for that group (see the [[admin: | ||
| + | - Save the report as a '' | ||
| + | - Now create or edit the user to which you want to apply these permissions to (double-click it in the list of users) | ||
| + | - Click on the // | ||
| + | - Hold down the //Shift// key on the keyboard and click on the **User permissions template** button at the bottom of the screen | ||
| + | - A file selection window will appear. Navigate to the csv file you saved in step 4 above, select it and click on the **Open** button | ||
| + | - The user template selection window will open with only one entry in the table. The entry has the name of the group you ran the permissions report for in step 3. Select that entry and click on the **OK** button | ||
| + | - The user permissions for all the tabs are loaded from the file and you see them set in the user's details window | ||
| + | - You can further edit these permissions if you wish or copy them to other stores (using the **Copy** button at the bottom of the window). When you are finished, click on the **OK** button on the user details window to save the permissions | ||
| ===== User license categories ===== | ===== User license categories ===== | ||