...
While we are still in the early stages, the goal is to create a minimal set of roles that . The roles could potentially expand as we learn more about customer usage.
...
We will grant access across all product areas including PlantUML, Glossary, and Dictionary with the following two roles.
Reader - read access to any content, both private and community. Will be able to perform collaborative tasks such as commenting and tagging.
Editor - all capabilities of Reader, in addition can manage content (e.g., create, update, delete, publish …) for all account-owned content.
Note:
At a later state we might split out roles by product, but as of now that use case doesn’t seem logical. If a person is an editor of PlantUML diagrams, they will most likely be an editor for Dictionaries.
Note:
community Community content can be read, commented on, voted on … but not changed unless owned by the account.
The concept of ownership needs to be fully fleshed out (person, account, org …), but not covered here.
The concept of how one can contribute to the community needs to be revisited (e.g. “known person”), but not covered here. Roles will allow the person to be an Editor, but steps still need to be taken to become a contributor.
In addition to the product-specific roles, there are two additional administrative roles and a special billing role:
Owner - can delete the account and add additional administrators.
Administrator - manages access - can assign other administrators as well as manage other team members such as inviting others and assigning roles.
Billing Administrator - manages subscriptions and billing.
Note:
the The Billing Administrator is a special role where the billing contact will be defined on the subscription page and not assigned as a particular team member since this roll role will not have any other functional needs other than to view and update subscription, billing, and usage.
when When CCH and Mapper are added, additional roles may be added that focus on the approval process.
...