Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Server permissions

In some organizations, it may be difficult, if not impossible, for permissions to be applied or exemptions made to enable wide ranges of users the “Logon as batch job” permission needed to run workflows in a Server with the current run-as credential capability.

 

If possible, could the Alteryx process still run as the server admin or "Run As" account, but enable the workflow to access the various different data sources (windows authentication) using specific credentials entered when running the workflow. So while the whole process runs as Service Account A, the access to databases, file systems, etc. may be done using their own specified credentials.

 

Some of this can be accomplished today by embedding credentials in database connections, but this isn’t an ideal scenario, and a more holistic solution that covers a wider array (or all supported) data sources would be preferred.