Changes between Version 4 and Version 5 of AuthModule/UserStories
- Timestamp:
- 2011-01-22T09:08:34+01:00 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AuthModule/UserStories
v4 v5 1 == Authentication and Authorization module user stories == 2 === As a user I want the module to have a set of permissions including read, write, execute and ownership. === 1 = Authentication and Authorization module user stories = 2 [[TOC()]] 3 == As a user I want the module to have a set of permissions including read, write, execute and ownership. == 3 4 Acceptance criteria: 4 5 * Please add! … … 7 8 * Extend Permission enum in DatabaseLogin to cover read, write, execute and ownership. 8 9 9 == = As a user I want the module to have a set of entities including tables, columns, rows and screens. ===10 == As a user I want the module to have a set of entities including tables, columns, rows and screens. == 10 11 Acceptance criteria: 11 12 * Please add! … … 15 16 * Create an interface Authorizable with fields owner: xref->!MolgenisUser, shareRead: xref->!MolgenisGroup, shareWrite: xref->!MolgenisGroup. 16 17 17 == = As a user I want the module to have a structure containing users and groups. Users can be part of groups. Both can have permissions on entities. If multiple permissions apply to an entity the narrower ones override the broader ones. ===18 == As a user I want the module to have a structure containing users and groups. Users can be part of groups. Both can have permissions on entities. If multiple permissions apply to an entity the narrower ones override the broader ones. == 18 19 Acceptance criteria: 19 20 * Please add! … … 25 26 * Make Molgenis check permissions via central class. (To be refined.) 26 27 27 == = As a user I want to be able to change permissions (grant, revoke) for the entities I own. The permissions are strictly limited to the entity. No information from linked entities will show up if permissions have not been given. ===28 == As a user I want to be able to change permissions (grant, revoke) for the entities I own. The permissions are strictly limited to the entity. No information from linked entities will show up if permissions have not been given. == 28 29 Acceptance criteria: 29 30 * Please add! … … 32 33 * Create a user interface to manage permissions for the entities owned by the user that is logged in. 33 34 34 == = As an administrator I want to be able to manage users and groups. ===35 == As an administrator I want to be able to manage users and groups. == 35 36 Acceptance criteria: 36 37 … … 53 54 * Make the login class to log in the public user by default. 54 55 55 == = As an investigator I want to be able to share the permissions on all entities belonging to my investigation with other users or groups. ===56 == As an investigator I want to be able to share the permissions on all entities belonging to my investigation with other users or groups. == 56 57 Acceptance criteria: 57 58 * I, Erik, can give my co-workers Despoina and Robert read-only access to all the features, values and targets belonging to my investigation AnimalDB.
