13
Insigths per role and status
Source: directus/directus#18958 · opened by @Pachat
Summary Not every one should see every insights Basic Example Certain dashboards may be under revision: they should have a status field Others could be reserved for certain roles: they should have role field Certain Query could vary among the roles, certain panels could be shown or not according to the roles, etc. Motivation Show to the user what he expects from its point of vue. Detailed Design To keep things simple just let us • edit the name of a dashboard • let us use add fields (as it is the case) but give the ability to edit them underneath the dashboard. • let us use sub-fields like $CURRENT_ROLE.quality in the queries (where quality is an added field to directus_roles) Requirements List Must Have: • A • B Should Have: • C Could Have: • D Won't Have: • E Drawbacks • Alternatives Create a dashboards collection that drives all the requirements by updating add…
No pledges yet. Be the first to back this.
Comments
Similar requests
Public policy doesn't show restricted role count
1 vote · 0 comments
Can't assign Public role from a policy
1 vote · 0 comments
Code-first configuration of schema, roles and permissions
274 votes · 0 comments
Manage Multitenancy with Users Logging in via Keycloak
1 vote · 0 comments
Extend the default role when registering
1 vote · 0 comments
No comments yet.