Community Requests

Provision users automatically from a SAML SSO provider.

I would like to specify more specific permissions for API access example, write only to drafts

The current limited palette causes overlap of the same colour for tags. An expanded colour picker would reduce the same colour being used for different tags.

Would be helpful for grouping diagrams in terms of project or collection.

Message queue object types that have a specific workflow.

Avoid accidental changes to global objects, or at least add an approval step. Standardize object meta-data and diagram layouts Possible RBAC benefit.

When I ha a system owned by a team, all app / stores / and components should be owned by the same team by default. Even being able to assign owner to domains diagrams would be nice with the same inheritance rules

Set user permissions per permission type. e.g. allow viewers to manage billing information, but not edit.

Inheritable edit permissions when assigning team ownership to an object.