Hi Scripting early adopters,
I am reaching out to coordinate on potential permission updates needed to your Workiva scripts.
File-level permissions will start being enforced for Workiva Scripts starting on the week of April 24th. You will need to make sure that every one of your scripts have the right permissions so that users currently interacting with the script have permissions to do so. You will need to do this to continue working with your Workiva scripts.
You should be familiar with how permissions are set for Workiva spreadsheets, presentations, and documents. You can currently do that for Workiva scripts too (see images below). But these permissions haven’t been enforced. They will start being enforced starting on the week of April 24th.
How can you be impacted when the permissions start being enforced?
- A common scenario is that users may be editing or running a Workiva script through the scripting editor. They may not be able to edit or run that script once permissions are enforced.
- Another common scenario is that a Workiva script may be being run from a Chain Scripting connector using specific user’s OAuth2 creds. That may stop working once permissions are enforced.
What to do?
- Please make sure that all your users currently interacting with Workiva scripts have the right permissions to access those scripts. And consider users interacting both via the UI and via APIs (ex: user’s OAuth2 creds used to run Workiva scripts from Chains).
- Both Workiva script current owners and anyone with Organization Admin role should be able to update permissions as required.
You can learn more about script-level permissions in the Intro to Workiva Scripting help article.
Don’t hesitate to reach back to me if you have any questions or concerns.
Thanks, and have an awesome day!