other_stuff:remote_authorisation

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 [2026/01/19 12:39] – [Assign the users as authorisers] Gary Willettsother_stuff:remote_authorisation [2026/01/19 13:03] (current) – [The authorisation statuses of requisitions] Gary Willetts
Line 17: Line 17:
   * Deny   * Deny
  
-===== Authorisation by masterlist/vertical program ===== +===== Authorisation by masterlist/vertical program or by store/facility ===== 
-In the remote authorisation module authorisers can only authorise the requisition lines which belong to items on the master list they are able to authorise for.+In the remote authorisation module authorisers can be set to authorise requisition lines which belong to items on the master list they are able to authorise for or which come from a particular store or facility. Or a combination of both!
  
 A masterlist can be used to represent a vertical program so this method can also be thought of as authorisation by vertical program.  A masterlist can be used to represent a vertical program so this method can also be thought of as authorisation by vertical program. 
  
-Authorisers can also be set up with **auto-authorisation**, where transactions will automatically be authorised if the user has not approved or denied the transaction before the set **auto-authorise period** has elapsed. +Authorisers can also be set up with **auto-authorisation**, where transactions will automatically be authorised if the user has not approved or denied the transaction before the set **auto-authorise period** has elapsed.
  
  
Line 124: Line 124:
 ===== Using the remote authorisation system ===== ===== Using the remote authorisation system =====
 ==== Requesting authorisation ==== ==== Requesting authorisation ====
-You do **not** need to request the authoristion of a requisition. When the remote authorisation system is turned on as described above, when a requisition that requires authorisation is **confirmed**, an authorisation request is automatically emailed to all active authorisers who are assigned to authorise a master list containing any of the items on the requisition.+You do **not** need to request the authoristion of a requisition. When the remote authorisation system is turned on as described above, when a requisition that requires authorisation is **confirmed**, an authorisation request is automatically emailed to all active authorisers who are assigned to authorise a master list containing any of the items on the requisition, and/or which is from the stores or facilities selected in their settings.
  
 The only types of requisition that can be authorised using remote authorisation are response requisitions created automatically in the supplying store in response to an internal order (internal orders are also called request requisitions). See the [[purchasing:ordering_from_one_store_to_another#internal_orders|6.04. Ordering from one store to another]] page for details on internal orders. The only types of requisition that can be authorised using remote authorisation are response requisitions created automatically in the supplying store in response to an internal order (internal orders are also called request requisitions). See the [[purchasing:ordering_from_one_store_to_another#internal_orders|6.04. Ordering from one store to another]] page for details on internal orders.
Line 144: Line 144:
 {{ :other_stuff:reg_auth_pending.png?600 |}} {{ :other_stuff:reg_auth_pending.png?600 |}}
  
-There is also an additinal Authorisation tab on these requisitions, which shows the authorisation history of the requisition:+There is also an additional //Authorisation// tab on these requisitions, which shows the authorisation history of the requisition:
  
-{{ :other_stuff:screenshot_2021-10-06_at_13.05.22.png?600 |}}+{{ .:pasted:20260119-125846.png?700 }}
  
-This particular screenshot shows that two authorisers have been requested to authorise lines on this requisition.+This particular screenshot shows that three authorisers at different levels have been requested to authorise lines on this requisition. The level 1 authoriser (user aaaa) has authorised the requisition, it is available and waiting for  authorisation by user bbbb (level 2). If they also authorised it then it will become available for user cccc (level 3) to authorise, bnut it is niot yet available to them. If emails have been sent to multiple authorisers at any level they will also be shown in the list.
  
 The authorisation status can have a few different values: The authorisation status can have a few different values:
  • Last modified: 2026/01/19 12:39
  • by Gary Willetts