Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To keep the stock scope simple for 3.1, the goal is to follow the pattern in Requisition to create similar Rights (permissions) that will be used by Stock in 3.1. This includes using the existing Home Facilities (for each user), Requisition Groups, Supervisory Nodes, and applying facility-specific permissionsand Supervisory Node heirarchy. This wiki page was originally created to design that in response to ticket 

Jira
serverJIRA (openlmis.atlassian.net)
serverId448ba138-230b-3f91-a83e-16e7db1deed1
keyOLMIS-2109
.

...

STOCK_INVENTORIES_EDIT (supervision type):
A user with this right can create a physical inventory and can submit a physical inventory within a specific Program and HomeFacility/NodeSupervisoryNode. What we mean by "HomeFacility/NodeSupervisoryNode" is that this right, just like any supervision type right, is assigned for a single Program along with either the users user's home facility or a supervisory node. If assigned for a Supervisory Node, the permissions apply to all facilities below that node in the hierarchy. The hierarchy may have multiple "child" supervisory nodes until it ultimately reaches Requisition Groups that contain one or more facilities. The STOCK_INVENTORIES_EDIT right only works with a single Program. So if a user should have permissions to conduct physical inventories for multiple programs, you would need to assign the right individually for each program to that user.

...