05 Feb 2026
07:19 PM
- last edited on
06 Feb 2026
08:04 AM
by
MaciejNeumann
Hi,
We have the workflows which are set as public are viewable and editable by the "Monitoring Viewer" users.
They are the read only users in Dynatrace and not suppose to edit any of the workflows.
Is it the expected behavior ?
Thanks,
Ram
Solved! Go to Solution.
05 Feb 2026 08:05 PM
Hello @RamkumarTIH you can configure your expected access using policies. Role Based Access like Monitoring Viewer is different from Attribute-Based Access Control is more granular. With this you can control the expected behavior of Dynatrace permissions.
https://docs.dynatrace.com/docs/shortlink/migrate-roles
05 Feb 2026 08:24 PM
Hi @DanielS - Does it mean by default "Monitoring Viewer" will be able to edit the workflows set as public ?
Do i need to create specific Attribute based access to restrict the workflow edit access for "Monitoring Viewer" users ?
05 Feb 2026 08:32 PM
Hi @RamkumarTIH I don't have a Vanilla tenant to check basic access but I can assure you that if you set a correct set of ABAC policies you can restrict all of this items:
13 Feb 2026 08:30 PM
Thanks @DanielS
I have assigned the in-built "Standard User" policy to the Operators.
Looks like below one is mandatory for users to access new UI..
//AppEngine
ALLOW app-engine:apps:run, app-engine:functions:run, app-engine:edge-connects:read;
Have created a custom Denial policy with the rules below and assigned to the group as i am unable to modify the default Standard user policy. Now Operators are able to access both old UI and new UI but with restriction to Workflows App and few others as per DENY statements.. Thanks for the help
//Davis
DENY davis:analyzers:read, davis:analyzers:execute;
//Davis Copilot
DENY davis-copilot:conversations:execute, davis-copilot:nl2dql:execute, davis-copilot:dql2nl:execute, davis-copilot:document-search:execute;
//Grail
DENY storage:bucket-definitions:read;
DENY storage:fieldset-definitions:read;
DENY storage:filter-segments:read, storage:filter-segments:write, storage:filter-segments:delete;
//AutomationEngine
DENY automation:workflows:read, automation:calendars:read, automation:rules:read;
DENY automation:workflows:write;
DENY automation:workflows:run;
//Extensions
DENY extensions:definitions:read;
Featured Posts