Our Orchestrator consists of several folders, each representing a department in our organisation.
Each of these folders has their own “local” administrators that are able to assign assets, load and run processes etc.
Now my question is if there is somewhere in Orchestrator that we (as “central” administrators) can save/store “locked assets”/credentials such as API-keys, so that we dont have to hard-code them when building the process.
Each sub-folder should be able to fetch the key when needed, but the “local” administrators should not be able to change/delete this key.
In Orchestrator, create a dedicated folder (e.g., “GlobalAssets”) where you will store the locked assets and credentials. This folder will have restricted access.
Add Global Assets:
Navigate to the “Assets” section within this folder and create the necessary assets, such as API keys and credentials.
Set Permissions:
Assign roles and permissions carefully. As central administrators, you should have full control over this folder. The local administrators of other folders should not have access to modify or delete these assets.
Can you be more specific in which permissions that would allow for this setup?
I have just tried creating an Asset in a folder and linking it to a department’s folder.
When changing to a user, that only exist in this department’s folder, I am still able to edit the asset.
