Is there a plan to limit the power user role when it comes to Approvals?
Summary:
Content (please ensure you mask any confidential information):
Hi all
At the moment we see these actions based on User roles:
These specific tasks are causing us problems with Auditors:
Administrator, Power Users, or the Last owner in the promotional path |
|
|---|---|
Is there a way to differentiate / limit the role of the power user so they do not unlock an approval if it has been locked by an Admin user?
Could the security Role become more granular in order to meet financial requirements?
Version (include the version you are using, if applicable):
24.09
Code Snippet (add any code snippets that support your topic, if applicable):
Tagged:
0