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:
Owner - full access to account and community
Contributor - full access to account
Reviewer - read and tag access to account (note: tagging or classifying will come later)
Reader - read access to account
In addition to the product-specific roles, there are two additional administrative roles:
Platform Administrator - manages access.
Billing Administrator - manages subscriptions and billing.
Product-specific Access
After looking the different jobs-to-be-done (JTBD), we identified the following access requirements:
Visibility: private, community or both
Ownership: Account-owned vs. not-account-owned or both