View Source

Which project roles have access to which tasks and features in the tool.

NOTE: Anyone with any permission on a project can at least view all public, private, and “In Development” reference sets in that project.

By role, users have the following access:

Guest:

Guest users can only see public, published reference sets.
What pages can guest users see?
- Library page (only shows public, published reference sets).
- Read-only Reference Set Details page for public reference sets.
Guest users cannot see the Project page or the Dashboard.
Can Guest users download public reference sets?
- RF2 – Yes
- Rf2 with Names – No
- List of SCTIDs – Yes
- Free Set – No
May view and download artifacts.
May compare and share a reference set.
May request access to a reference set.
May download Members table.

Viewer:

May view a reference set in read-only, including workflow history, notes, and audit trail.
May view all public feedback discussions/replies for a member or reference set, as well as any private discussion/reply in a reference set for which they are a member.
May create a new public or private discussion/reply for a member or reference set.
May edit/delete their own discussion/reply for a member or reference set.
May view and download artifacts.
May compare, download, and share a reference set.
May view member table or taxonomy, including member history, as read-only; as well as download the member list.
May request access to the underlying project of a reference set.

Author:

May edit the reference set, including editing the metadata, adding authoring notes, and converting an Intensional reference set to Extensional.
May advance the workflow, request review or publication, or withdraw a request (at any point before the reference set advances to the next workflow state).
May upgrade a reference set.
May add, edit, delete, and download artifacts, and add and reply to reference set feedback.
May add/remove members from a reference set.
May delete In-development Versions of reference sets and Inactivate reference sets.
May view all public feedback discussions/replies for a member or reference set, as well as any private discussion/reply in a reference set for which they are a member.
May create a new public or private discussion/reply for a member or reference set.
May edit/delete their own discussion or reply for a member or reference set.
May view member history, as read-only, as well as download the member list.
May view audit trail, as well as compare, download, and share a reference set.
May request access to the underlying project of a reference set.

Reviewer:

May advance workflow (accept and send for publication), reject the reference set, or un-assign the reference set.
May add review notes (required when rejecting a reference set).
May view all public feedback discussions/replies for a member or reference set, as well as any private discussion/reply in a reference set for which they are a member.
May create a new public or private discussion/reply for a member or reference set.
May edit/delete their own discussion/reply for a member or reference set.
May view and download artifacts, as well as view audit trail, workflow history, and notes.
May view member table or taxonomy, including member history, as read-only; as well as download the member list.
May compare, download, and share the reference set.
May request access to the underlying project of a reference set.

Admin (Admin for the Team):

May invite a user to join the organization as a collaborator.
May view all public and private feedback discussions/replies.
May create a new public or private discussion/reply.
May edit/delete any feedback discussion/reply, including their own.
May add and reply to reference set or member feedback.
May view a reference set in read-only, including workflow history, notes, and audit trail.
May compare, download, and share a reference set.
May view and download artifacts.
May view member table or taxonomy, including member history, as read-only; as well as download the member list.
May return a reference set that is "In Edit", in the workflow status to "Ready for Edit" by undoing or saving any changes done by the author.
May cancel a reference set that is in Upgrade.
May un-assign a reference set from the author to "Ready for Edit".

Admin Dashboard/Settings Access (Admin for the Organization):

Admin may edit Project settings including roles associated with Organizations, Teams, and Users.
Each time an Organization is created, an admin Team (Administrator(s) for the Organization..) will also be created with the Organization creator as a member.
The admin Organization Team may only administer the Organization it was created for.
Only admins for the Org can create/update: Users, Teams, Projects, and Organizations (can only edit, not create Organizations).
Only admins will see the configuration button in the left sidebar to open the Organization/Team/Project Configuration pages.
Users may be added to an Organization on the Organizations-User page.
After users are added to the Organization, they may be added to a Team on the Teams-User page. NOTE: Being a member of an organization gives a user no permissions. Membership in a Team is what assigns user permissions. A user who belongs to an Organization but is not on a Team in the Organization would not be able to see private reference sets.
Admin can only see and perform actions based on their permissions. An admin user could submit an action, but if they did not actually have permission to perform that action, that backend would reject the submission.
Only Organizations and Projects you have permission to view or to admin will appear in your dashboard.
You can only create Teams for Organizations that you can admin, meaning "be-all-admin" role for example.

Super-User ("all-all-admin", or "all-all-all" permissions):