Forum Discussion
Connection Access
- 7 months ago
Hi there, this is extremely common in workspaces where the items and associated connections were first created with a service principal and then the branching off was done manually.
First you can check to see if somebody has permissions to access the connection in "Manage connections and Gateways" and then see if they can assign you permissins.
Ongoing, if the way to create the items is automated ensure the process also adds additional permissions to the connections. If done manually, ensure whoever adds them goes to "Manage connections and Gateways" and adds the relevant permissions.
I hope this helps resolve your issues long-term.
Hi there, this is extremely common in workspaces where the items and associated connections were first created with a service principal and then the branching off was done manually.
First you can check to see if somebody has permissions to access the connection in "Manage connections and Gateways" and then see if they can assign you permissins.
Ongoing, if the way to create the items is automated ensure the process also adds additional permissions to the connections. If done manually, ensure whoever adds them goes to "Manage connections and Gateways" and adds the relevant permissions.
I hope this helps resolve your issues long-term.
Thanks for your response...it is much appreciated!
The issue was that one of the developers created a few connections and did not share the connections with the security group for the development team. It meant that he was the only one able to sync his feature branch with his workspace and everyone else was getting the error I posted.
Now I can sync my feature with my workspace successfully
Thanks once again!