There are several ways to determine who can perform workflow transitions. If no script or just a general permission is used, anyone can do the work. Typically we see a condition script that blocks the transition and then will allow a user (usually based on a field set on item details).
Another method is to use a separate workflow permission; assign that permission to a role and group and have that drive who has the rights to promote a workflow (this works best when it’s not record level dependent, but more across the entire workspace where anyone in the group can review and make the workflow decisions).
In this example, I set up a separate permission in my Change Order workspace for just Change Analysts; I assign this to the relevant workflow transitions and a different role (so just those in the groups that have that role can perform):
This way you aren’t using a named user, but it’s more controlled from the security settings.
A third option is to consider using a reference workspace (maintained by admins or power users) with the team list of users.
Want to learn more about how other Fusion Lifecycle customers are setting up access controls for their sites? Join us in Boston next month for our fourth annual Accelerate Conference.
--Michelle, Fusion Adoption Team
Comments