Skip to main content
C1 provides identity governance for Octopus Deploy. Integrate your Octopus instance with C1 for unified visibility and governance over user access.

​
Capabilities

The connector reads one Octopus Deploy instance. It syncs that instance’s users and teams — both instance-wide teams and teams scoped to individual spaces — along with each team’s membership. Users sync as enabled or disabled based on their active state in Octopus, and service accounts are labeled as such. The built-in Everyone team includes every user on the instance by definition, so the connector reports each user as a member of it. Teams mapped to external directory groups (Active Directory or Microsoft Entra ID) carry those mappings as team attributes for visibility; membership conferred through an external directory group resolves inside Octopus at sign-in and is not expanded into individual memberships.

​
Gather Octopus credentials

The API key’s owner needs permission to view users and teams across the instance. Membership in the built-in Octopus Administrators or Octopus Managers team covers this. A key created by a user without those permissions cannot list other users and does not work with this connector.
1
Sign in to your Octopus instance as a user with permission to view users and teams, or use a service account with those permissions.
2
Open your avatar menu and go to Profile > My API Keys (for a service account, open the account under Configuration > Users and find its API Keys section). Click New API Key, give it a purpose, and create it.
3
Copy the key when it is shown — Octopus displays it only once — and note your instance’s base URL. For Octopus Cloud this is https://<instance>.octopus.app; for self-hosted Octopus Server it is your own address, including any virtual directory the server is installed under.

​
Configure the Octopus connector

Follow these instructions to use a built-in, no-code connector hosted by C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Octopus and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter the Octopus credentials:
  • Octopus base URL: your instance’s address, with no trailing slash. For example, https://mycompany.octopus.app.
  • API key: the API key created from your profile or service account.
9
Click Save.
10
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Done. Your Octopus connector is now pulling access data into C1.