Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
other_stuff:remote_authorisation [2025/03/18 16:23] – [Authorising using the web app] Gary Willettsother_stuff:remote_authorisation [2025/10/01 04:09] (current) – [Assign the users as authorisers] Jonna Quismundo
Line 5: Line 5:
 mSupply has features to allow various types of transactions to be authorised within the application before they affect stock so that supervisors can make sure the transactions are correct (see the [[other_stuff:invoice_authorization|]] page for details). mSupply has features to allow various types of transactions to be authorised within the application before they affect stock so that supervisors can make sure the transactions are correct (see the [[other_stuff:invoice_authorization|]] page for details).
  
-**Remote authorisation** allows supervisors to authorise **Response requisitions** //via a web app//, so that they can participate in the authorisation process without having to login to mSupply.+**Remote authorisation** allows supervisors to authorise **Response requisitions** //via a web app//, so that they can participate in the authorisation process without having to login to mSupply. The process described below uses a supplier and customer store in the same mSupply installation but it can work with stores in different mSupply installations using [[:supplier_hub|mSupply Link]].
  
 <WRAP center round important> <WRAP center round important>
Line 71: Line 71:
  
 This will enable them to receive emails when a requisition is awaiting their approval. This will enable them to receive emails when a requisition is awaiting their approval.
 +
 +<WRAP center round important 60%>
 +The user must also be assigned to one store as a `default` login. This is needed for the login to the web portal to work.
 +
 +{{ :other_stuff:userneedstohaveonesiteas_default-2025-08-26.png?600 |}}
 +</WRAP>
 +
 +
  
 === Assign the users as authorisers === === Assign the users as authorisers ===
Line 83: Line 91:
 **New button:** Click on the New button to assign a user as an authoriser. This window will open: **New button:** Click on the New button to assign a user as an authoriser. This window will open:
  
-{{ :other_stuff:screenshot_2021-10-05_at_12.57.13.png?400 |}}+{{ :other_stuff:remoteauth.png?400 |}}
  
   * **Authoriser:** Enter the name of the user here. Type the first few characters of their username and press the Tab key on the keyboard to select the user from a list of users with usernames that start with what you have typed.   * **Authoriser:** Enter the name of the user here. Type the first few characters of their username and press the Tab key on the keyboard to select the user from a list of users with usernames that start with what you have typed.
Line 90: Line 98:
     * **Auto-authorisation period (days):** The number of days after which any requisition lines waiting for authorisation by this user will be automatically authorised by the system.     * **Auto-authorisation period (days):** The number of days after which any requisition lines waiting for authorisation by this user will be automatically authorised by the system.
   * **Active:** This is checked by default. If this is checked then the user's assignment is active and they can act as an authoriser. If it is not checked then the user cannot act as an authoriser. This is useful when an authoriser is to be removed as an authoriser for a period of time and then added back in again e.g. when they go away on holiday.   * **Active:** This is checked by default. If this is checked then the user's assignment is active and they can act as an authoriser. If it is not checked then the user cannot act as an authoriser. This is useful when an authoriser is to be removed as an authoriser for a period of time and then added back in again e.g. when they go away on holiday.
 +  * **Store approval:** This is not checked by default. If this is checked, you can set the rule to only need approval if the request comes from the stores checked in the list. If store approval and no masterlist is set, then all items for the requisition need approval. If masterlist and store approval are both set, then only require approval if from the requesting store and if the item is part of the masterlist. A request from facility (not a store) can also be included by adding a tag "remoteAuthorisation" in the name.
  
 Click on the **OK** button to save the new assignment or the **Cancel** button to cancel it. Click on the **OK** button to save the new assignment or the **Cancel** button to cancel it.
Line 95: Line 104:
 **Editing an authoriser assignment:** Double-clicking one of the users in the list will allow you to edit the assignment; the 'Add assignment' window shown above will open, populated with the current settings for the user. Edit the settings to be what you wish and click on the **OK** button to save your changes..  **Editing an authoriser assignment:** Double-clicking one of the users in the list will allow you to edit the assignment; the 'Add assignment' window shown above will open, populated with the current settings for the user. Edit the settings to be what you wish and click on the **OK** button to save your changes.. 
  
 +
 +<WRAP info center round 90%>
 +There is a preference to allow authorising an item only once, even if it is part of two or more master lists.
 +Pref > Misc > If an item belongs to multiple master lists and authorisers, only one authorisation is required.
 +</WRAP> 
  
 ====Enable emailing of authorisers==== ====Enable emailing of authorisers====
Line 185: Line 199:
 |  //  Previous:  **[[other_stuff:invoice_authorization]]** | | Next: **[[other_stuff:misc_labels]]** //  | |  //  Previous:  **[[other_stuff:invoice_authorization]]** | | Next: **[[other_stuff:misc_labels]]** //  |
 ---- struct data ---- ---- struct data ----
-pagestatus.status    : +pagestatus.status    : All Good
 ---- ----
  
  • Last modified: 2025/03/18 16:23
  • by Gary Willetts