...
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.
Administrator - all capabilities of Editor, in addition can assign other administrators as well as manage other team members such as inviting others and assigning roles.
Owner - all capabilities of Administrator, in addition can delete the account.
Billing Administrator - manages subscriptions and billing.
Note:
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 role will not have any other functional needs other than to view and update subscription, billing, and usage.
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.
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 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 role will not have any other functional needs other than to view and update subscription, billing, and usage.
When CCH and Mapper are added, additional roles may be added that focus on the approval process.
...
Description of the two functional roles not taking scope into account at this time.
Role
Description
Actions
Comments
Role | Description | Actions | Comments |
|---|---|---|---|
Reader | Read access to all account-owned content (PlantUML, Glossary, Dictionary …) whether private or community. | Read. | Collaboration capabilities such as commenting will be added later. |
Editor | Edit access to all account-owned content (PlantUML, Glossary, Dictionary …) whether private or community. | All functional tasks (create, update, delete, publish …). |
Glossary - Scope
Glossary may need to have Scope defined early on to ensure only specific users can access sensitive information. However, we won’t focus on that yet.
Administrative Roles
Regardless of the products subscribed to, administrators are required to set up the account and grant access to users.
Administrator
Manages access to the application.
Manage users (invite, revoke, remove …).
Administrator | Manages access to the application. | All functional tasks plus manage users (invite, revoke, remove …). | |
Owner | Manages all IT Infrastructure including SaaS applications. |
Delete the account and add/remove other administrators.
All functional and administrative plus able to delete the account. | |||
Billing | Manages all financial related topics including SaaS subscriptions. | Choose and pay for subscription. |
Glossary - Scope
Glossary may need to have Scope defined early on to ensure only specific users can access sensitive information. However, we won’t focus on that yet.
Jobs to Be Done (JTBD)
Below are the identified jobs that need to be done with their respective permission-based roles.
...