Workflow of assigning organisation roles and content roles
Hi @lathrops1
(cc @John.kopanas, @danjela, @henrik, @yannis)
Based on our discussion in the progress review call about the confusion over 'team' versus 'roles', we have designed these changes to the organisation page. Please review this closely with your team.
Organisation's users page
An organisation's users now has its own page.
- We've changed the column name from "Team" to "Roles" and combined the admin column since this represents organisation roles. The Admin role will be displayed first in this column.
- We've changed the bulk action button from "Team" to "Assign roles"
Edit user modal
- Currently, it isn't possible to open the 'Edit User' modal unless the user has been accepted to the org. As explained in #36 (closed), clicking on a user's row will now open the modal, so the System admin can accept a single user and assign the "Org admin" role, and any other roles, at the same time.
- All organisation roles are shown together under the heading "Organisation roles"
We considered how to show a user's content roles in the table view, but ultimately tying to fit this detail into a table would detract from the purpose of showing an overview. Instead, scrolling down, the Admin will see the user's content roles. This will list all the books and collections that the users has been associated with. The Admin can also go through the user cards to see this detail for each user by using "next" and "previous", instead of having to open and close each one.
Dashboard: New book modal
The current development of the New book modal demonstrates one purpose of assigning organisation roles on the Admin page. Those users who have been assigned the role "Org admin" and "Editor" see the 'New Book/Collection' button because these roles have the permission to create new books and collections for their organisation.
Book Manager and Collection Manager
Once a book or collection has been created, the Org Admin and Editor can assign users to content via the 'Team' modal, individual rows or the bulk actions bar. (We think using the word 'Team' makes sense here as the team working on this book/collection, but please let us know if you disagree).
Content roles can be assigned per book and per chapter. Permissions for books versus chapters should be managed separately in the UI:
- Users assigned via the 'Team' modal have access to the book
- Users assigned via the individual chapter row (modal/card or expand row design TBD) have access to that chapter
- Users assigned via the bulk action bar have access to the selected chapters.
Since users already have organisation roles, the list of users to assign to content can be limited by the organisation role.
We have a draft of this design but there are some use cases to work through:
- As an Editor, I need access to the full book so I can see and edit any chapter, and assign other users to these chapters -- is this always the case, or will some editors only need chapter level access?
- As an Editor, I want an overview of all the team members working on my book, including whether they have access to the full or individual chapters.
- As an Author, I need access to the full book so that I can upload new chapters and view my chapter in context.
- As an Author, I should only be able to edit chapters that I have uploaded or been assigned to by the editor.
- As an Author, I want to suggest a reviewer for my chapter -- is this applicable?
- As an Reviewer, I only want to see the chapters that I've been assigned to review. -- is this always the case, or will some reviewers need book level access?
Team modal
In this view, the author assigns users to the book, and can see an overview of the full team.
Assign to chapters bulk