-
Notifications
You must be signed in to change notification settings - Fork 0
User Roles
This document identifies the various roles that may be assigned to AskNature users and defines the parameters associated with each role.
Initially, AskNature is being relaunched with four user roles that each build on the capability of the last: unregistered, participant, editor, and admin. Generally, unregistered users are able to view all public content, participants are able to create/edit/archive their own content and create relationships between their content and other public content, editors are able to create, update, and archive all content, and admins are able to do all this plus create/modify/delete users (including role assignment) and delete all content types.
These roles are described in more detail below:
- Read all public navigation and detail views.
- Includes public profile information associated with each user.
- See disabled tools available to reader users (tapping these tools will prompt users to create an account).
- Create new participant accounts.
- Granted a short-term (three day) generic session based on IP that transfers any relevant activity/data [define this] to new accounts.
- "Like" or provide other positive tap-based feedback on relevant content.
- Share content.
- Default role for all user accounts migrated from existing legacy site.
- Create new content entities:
- Biological Strategy
- Inspired Solution
- Source
- Context
- Researcher
- Collection
- Media
- Designed System
- Comments (Inspired Ideas, Comments, etc)
- Create relationships between content they have created and all public content.
- Update all content entities and relationships they have created.
- Includes adding/removing relationships between public content and personal Collection/s.
- Includes updating their user profile.
- Archive all content entities and relationships they have created.
- Important: All new content and relationships remain in "pending_approval" status and are only visible to the author, editors, and admins until an editor or admin has manually "approved" at least one piece of content created by the author.
- Note: Each content and relationship entity created by probationary participants appears in a queue on a console visible to editors and admins. Once at least one entity has been approved, the author's account is upgraded from probationary to approved and all remaining new content from that author is automatically approved.
- All new and updated content and relationships are instantly approved.
- Flag content as inappropriate (when available).
- Annotate content (when available).
- Note: An editor or admin may place any approved participant back on probation at any time, at which point any new content created by that participant will again be subject to manual approval.
- Read all editor console views.
- Note: Includes tabulated list views of all content, relationship, and user entity types.
- Note: Includes moderation console.
- Note: Includes global activity feed.
- Read tabulated content in all detail views that expose retrieved JSON data.
- Read editorial flags, comments, and approval status on all entities.
- Create new content entities as "AskNature Team" user:
- All entities participants can create, plus:
- Living System
- Create participant user accounts.
- Create relationships between all content as "AskNature Team" user.
- Update all content entities and relationships owned by "AskNature Team" user (encompasses all previously unassigned entities).
- Update editorial flags, comments, and approval status on all content and relationship entities.
- Archive all entities and relationships owned by "AskNature Team" user.
- Reassign content ownership from "AskNature Team" user to any other user (this can only be undone by an admin or the user receiving ownership).
- Moderate entities created by probationary participants.
- Note: Approving an entity removes a participant's probationary status.
- Add probationary status to any participant.
- Add removed status to any participant.
- Create participant, editor, and admin users.
- Read and Update all public and private profile information in all participant and editor user accounts.
- Update role and status for all participants and editors (includes promoting users to admin).
- Update any entity, except other admin users.
- Archive any entity, except other admin users.
- Delete any entity, except other admin users.
- Update, Archive, and Delete any admin user.
In the future, expect a more nuanced expansion of participant and editor role types, along with sets of permissions tied to group creation and management.
Note that the legacy site already has a number of existing roles defined, which will not be propagated to the new site. These existing roles include:
- Administrator
- Editor
- Metacurator
- I4c
- Moderator
- Photocurator