I'm working on a JE approval workflow. I'd prefer to have the workflow "run as admin", since it utilizes a number of custom fields that I don't want most users to see/have access to. However, the trouble is that when you run as admin, anyone who approves journal entries via my workflow can post to locked periods (since Administrators have the Override Period Restrictions permission), and I'd like my workflow to respect locked periods. Anyone run into this issue before or have any thoughts on how to tackle it?

Why not hide the custom fields from the forms so it would not be visible to most users? You may have the work of juggling multiple forms, but that would allow you to run the workflow with enabling "Run as admin"

We did actually have this exact problem. We tried running the WF as full Access and that Solved that specific problem but created a new one with other permissions so we ended up creating a custom role for the workflow that had only the permissions it needs.

@Sean Murphy Yeah, that's the same resolution I came to the last time I dealt with this problem, but it's a rather clunky/annoying solution. I may end up going with what @thomas suggested in this case, I just really hate hiding things from the UI as a method of "securing" them.

good luck with which ever way you go

Good luck!