Quote from Lakshmi's email but made a few changes of the right matrix table:
Stock line Item
Create | Submit | Reverse | View | |
Stock line item _ create | ☑️ | ☑️ | ☑️ | |
Stock line item _ reverse | ☑️ | ☑️ | ||
Stock line item _ view | ☑️ |
Stock Card:
| Create | Archive | View | |
|---|---|---|---|
| Stock card_create | ☑️ | ☑️ | |
| Stock card_archive | ☑️ | ☑️ | |
| Stock card_view | ☑️ |
A few points of discussion:
- · I haven’t added anything around authorizations here – the PC discussion concluded we might eventually want the ability for someone to audit/confirm a periodic physical stock count, but that none of the other movements need approvals. Since we’ve tabled that for later, I suggest we look at what the rights structure for that story would be while researching the story.
- · Ashraf had also mentioned sometimes large adjustments/stock movements needing extra information. I wonder if a “stock management_request info” right might be appropriate where the user has the right to send a message to the creator of the movement to provide additional information.
- · I assume any rights around notifications will be handled by that Epic.