Open saracarl opened 2 years ago
My answer:
A single organizational account -- which can be an individual product owner or a service account -- can create collections (our word for thematic projects) and add additional accounts as staff members on those collections. Staff can do everything but delete the collection. Once someone has been added as a staff member they have the ability to create additional collections which show up under the main organizational account.
Issues to address: making staff without adding to a collection; removing staff when they leave.
Maybe change "Add Owners" in the settings to "add staff"
Show "staff" under your owner profile? And which collections they have access to?
See also #1411 if we address this.
Both staff and reviewers should be managed at the owner account level (a dashboard?)
LVA specifically asked for this.
The one scenario in which this staff/org mapping may be a challenge is where one user should be able to receive activity email for one collection but not others. To do: review data to see how common this actually is.
It turns out I did not understand the idea of staff accounts. It sounds like "staff" is a role within an organisation account, but in our installation my (admin) account is a staff account that is not strictly linked to another account. @benwbrum pointed to this issue because a private document set that I created in my own private collection suddenly had a completely different owner who has no relation with or access to my private collection. I traced that behaviour back to #2075, from which I learned that staff accounts are special.
We need better management of staff on organization accounts. Question from an opportunity: