The problem it solves: There was no dedicated role for managing connections in Access Management. To let someone edit connections, you had to grant them a broader role — over-granting permissions they didn’t need, just to cover one task. That worked against least-privilege access control and made permissions harder to audit.
What we built: A new Connection Editor role that grants connection-editing access precisely, with no side effects on other permissions. An administrator assigns the Connection Editor role to the users who manage connections — giving them exactly the access they need and nothing more.
What this means for your team
Least-privilege by default
Grant connection editing without opening up anything else.
Cleaner access control
One role, one clear responsibility, easier to audit.
No workarounds
Stop using a broader role as a stand-in just to cover connection management.
Audience at a glance
| Role | Primary action |
|---|---|
| Administrator | Assign the Connection Editor role to the users who manage connections; review and tidy existing connection-editing permissions. |