...
Visibility: private, community or both
Ownership: Accountaccount-owned vs. not-account-owned or both
Actions: create, read, update, delete, tag, classify, comment …
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.
Role | Description | Visibility | Ownership | Actions | Scope | Comments |
|---|---|---|---|---|---|---|
PlantUML Owner | Access to all private and community diagrams | Private and Community | Account-owned and not-account-owned | All (create, update, delete, …) | All (any PlantUML diagram) | |
PlantUML Contributor | Access to all account-owned diagrams whether private or community | Private and Community | Account-owned only | All (create, update, delete, …) | All (any PlantUML diagram) | |
PlantUML Reviewer | Review access to all account-owned diagrams whether private or community | Private and Community | Account-owned only | Read and comment | All (any PlantUML diagram) | Their role-specific actions such as comment won’t be available early on which makes this role identical to “reader” |
PlantUML Reader | Read access to all account-owned diagrams whether private or community | Private and Community | Account-owned only | Read | All (any PlantUML diagram) |