If I create an integration service connection on my personal workspac,e I cannot use it to ran an attended automation that’s deployed in another folder
I would like for my connection to be usable in another folder, but only by me - even if other people have access to the said folder
Is this possible ? or is there a similar way to safely share a personam integration connection without risking it to be misused
I think what you want might already be the default behaviour, connections created inside a folder belong to whoever created them, they only become usable by others if you explicitly share them. So maybe try creating the connection directly in that target folder instead of your personal workspace, and just dont share it
if thats how it works there, other people with folder access would see the automation but would have to create their own connection to run it, and yours stays yours
im not 100% sure it behaves like that on every connector though, so before relying on it id ask a colleague who has access to that folder to open the automation and check if your connection shows up for them or not. That test answers it in a minute
As far as I know, an Integration Service connection created in your personal workspace is tied to your user, so it may not be directly available to an automation deployed in another folder.
If you want to use the connection only by yourself, you can check the folder/user permissions and give access only to your user. This way, the connection can be used where required without giving other users access.
Also, make sure the connection is not shared at the folder level with other users, otherwise they may be able to use it.
Integration Service connections work as all or nothing per folder. Please find the details of when to use Personal and Shared connections below.
Personal workspace connection are used only within your personal workspace, not in other folders (even by you). Personal workspace connection can be used only if you provide permission to other folder, however everyone in the folder can access it. If the automation supports it, run it from your personal workspace instead of the shared folder.
Shared folder connection are used by everyone with access to that folder, with no per-user restriction. There is no “shared to a folder, but locked to one user” as of today. If the automation must run from the shared folder then its recommendation to only put service account-based connections in shared folders, precisely because shared is accessible to all.