Suggested format for use cases is user story: As a < type of user >, I want to < specific goal >, so that < the reason >
Other possible formats:
- application activity: list of specific activities which require individual permission
- i.e. edit metadata (without editing other object attributes)
- access grid format: list specific application tasks in rows, and user roles in columns. Check the intersection of roles and tasks
Organization | Use Cases
|
---|---|
UNC | https://docs.google.com/document/d/1gAu5HNLBEKnLtwVY_FKTzy5FbD4TWCV8vwOoWpU6fmk/edit |
Emory | Draft user profiles for Repository Management (local effort to inform roles/permissions needed; Deposit-related profiles forthcoming) |
Emory | Permissions Matrix template (in progress through March): entities, verbs, roles |
Emory | Additional user stories (in progress through March) - some stories may change as we learn the Hyrax permissions model |