We ahve the following orchestrator folder organization:
each has their default orchestrator personal workspace where they can create their integration service connections
the citizen attended automations however, are published into a dedicated shared folder (let’s called it “Attended Folder”)
When creating a connection, should it then be created in the target Attended Orchestrator folder where the automations are published, or still be created in personal workspace?
If they are created in personal workspace, can they still be called from a different folder when ran by the concerned user?
No, a connection created in a user’s personal workspace, with no sharing configured, cannot be called from a different folder even by the same user. You will have to either create it in the target folder or explicitly share to that folder.
You have 2 options here:
(Recommended Approach) Create the connection directly in the Attended Folder. Since it’s a shared folder, all users with access can use/edit it.
Use Connection Sharing - create the connection wherever convenient and explicitly share it with the Attended Folder/user/group. This is exactly what the “Connection Sharing” feature is for, sharing a connection across folders without duplicating it.
Prashanth’s answer covers the folder mechanics correctly, just want to flag one thing specific to Outlook that trips people in this exact citizen dev setup..
Outlook connection in Integration Service are usually OAuth tied to one mailbox. the person who authorized it. So if the idea is that each citizen automation sends or reads mail as that specific user, a single connection created in the Attended Folder and shared to everyone would actually send everythin from whoever authorized it, not from each citizen’s own mailbox
if that’s the case, what works better is each citizen creating their own connection in personal workspace authenticated as themselves, then using Connection Sharing to expose just that one connection to their own automation in the Attended Folder, not sharing one single connection to the whole group. A bit more setup upfront but it keeps the mailbox identity correct per user
if instead all citizen are fine sending from one shared mailbox or service account, then Prashanth’s option 1 is simpler and just works
to add access, go to Integration Service, Connections tab, select your connection and look for the folder/sharing option there, it lets you add the Attended Folder to it without duplicating the connection. The exact button label might differ a bit depending on your Orchestrator version, but its under that connection’s settings
and yes, once shared it becomes usable in that folder just like a connection created there directly, so it will show up in Assistant for whoever has access to Attended Folder
one thing to keep in mind, the original workspace still owns it under the hood, so if that gets removed later the shared connection can break too. Thats why alot of people just create it straight in the Attended Folder instead, skips that dependency
if the sharing option isnt where you expect, the Orchestrator user guide has the exact steps for your version, worth a quick check before relying on my description here
