Admin can create a new role allowing no access, read, write, and delete at the record level

User Story

An administrator can create a new role that allows users assigned that role to:

• Have no access at the record level (e.g. no access to loan records)
• Have read access at the record level (e.g. may view loan records but not edit them)
• Have write access at the record level (e.g. may view and edit loan records)
• Have delete access at the record level (e.g. may delete loan records)

Note: If a user has been assigned a "no access" role at the record level, those records should not appear in that user's search results, as tabs in the user interface, or as links in the right sidebar.

For release 0.7, the record level is inclusive of: Objects, procedures, and media records.

Related User Stories:

• Admin can create a new role allowing read or write at the field level
• Admin can create a new role allowing read , write, or delete at the vocabulary term level
• Admin can create a new role allowing "authorization" at the vocabulary term level

Derived Stories:

These related stories are created or derived from the User Story described on this page. For example, Service Stories describe bits of functionality that a service might need to provide in order for the User Story requirement to be fulfilled. These stories are used to create, plan, and track specific development tasks in JIRA. If development has begun on one of these stories, there should be a link into JIRA describing the story and the related development tasks.