Editor access and permissions on collections and its members
As confirmed in #832 (comment 74879)
As with any book, relevant team members should be added to the collection to give them access. Roles that need access
- Previewers (unclear at this stage)
Follow same approach as books
- team button open team modal
- Sys admin or Org admin adds 'Editor' users from the Organisation to the collection
- What actions can the editor take at collection level?
- what actions can't the editor take at collection level?
- If Editor has access to collection, should they automatically get Editor access to all the books in the collection?
Same teams component as books
Implementation (if applicable)
[A description of the steps to implement the feature.]
Alternative approaches (if applicable)
[Include any alternatives to meet this use case.]
Open issues (if applicable)
[Links to and a discussion of related issues, if applicable.]