Roles and Permissions

As we roll out the UC 5.0 platform including PlantUML, Unified Dictionary, API Access and more, we will be putting in place an initial set of permission-based roles to manage access to the application functionality.

While we are still in the early stages, the goal is to create a small set of roles and potentially expand as we learn more about customer usage.

Overview

For each of the initial areas: PlantUML, Dictionary, and Glossary we want to grant access in similar fashion across those areas with the following roles:

1. Owner - full access to account and community

2. Contributor - full access to account

3. Reviewer - read and tag access to account (note: tagging or classifying will come later)

4. Reader - read access to account

In addition to the product-specific roles, there are two additional administrative roles:

1. Platform Administrator - manages access.

2. Billing Administrator - manages subscriptions and billing.

Product-specific Access

After looking the different jobs-to-be-done (JTBD), we identified the following access requirements:

1. Visibility: private, community or both

2. Ownership: account-owned vs. not-account-owned or both

3. Actions: create, read, update, delete, tag, classify, comment …

4. Scope: specific object access (e.g., “glossary A”, “dictionary C”, “PlantUML Diagram 1” …)

Discussion topic: Many modern SaaS applications include collaboration aspects where users can individually grant access to specific documents, diagrams … for others to comment or edit. How does scope and collaboration work together? Or are they the same thing?

PlantUML

PlantUML access need not have Scope defined for early access, but will likely be needed for GA.