ConductorOne docs

Set up a Slack Enterprise Grid connector

ConductorOne provides identity governance and just-in-time provisioning for Slack Enterprise Grid. Integrate your Slack Enterprise Grid instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Yes, there are TWO kinds of Slack integration! The instructions below integrate a Slack Enterprise Grid account with ConductorOne so that you can review access data and grant user access to Slack. (We also have an integration for Slack Pro and Business+ accounts.)
If you want to install the ConductorOne Slack app, so that you and your colleagues can request access and get notifications about new ConductorOne tasks in your Slack workspace, go to the Settings page in ConductorOne and click Notifications.

Capabilities

Resource	Sync	Provision
Accounts	✅
Workspaces	✅
User groups	✅	✅
Workspace roles	✅	✅
Enterprise roles	✅

Gather Slack Enterprise Grid credentials

Configuring the connector requires you to pass in credentials generated in Slack Enterprise Grid. Gather these credentials before you move on.

A user with the Org owner role in Slack Enterprise Grid must perform this task.

Create a ConductorOne app in Slack Enterprise Grid

Make sure you are signed into your Slack Enterprise Grid account, then navigate to api.slack.com/apps/.
Click Create an App and select the From scratch option.
Give your new app a name, such as “ConductorOne integration”, and select a workspace you want to integrate with ConductorOne (later we’ll install the app org-wide).
Click Create App.
Your new app opens. From the menu on the left, select Org Level App and Enable org-readiness.
Select OAuth & Permissions from the menu on the left.
In the Redirect URLs section of the page, add https://conductorone.com as a new redirect URL.
Scroll down to the Scopes section of the page. In the Bot Token Scopes area, add the following OAuth Scopes:
- channels:join
- channels:read
- groups:read
- team:read
- usergroups:read
- users.profile:read
- users:read
- users:read.email
In the User Token Scopes area, add the following OAuth Scopes:
- admin
- admin.roles:read
- admin.teams:read
- admin.usergroups:read
- admin.users:read
- admin.users:write

Install the ConductorOne app org-wide

You must now install the new app org-wide so that ConductorOne can sync data from all of your organization’s workspaces.

While still on the OAuth2 & Permissions page, scroll up to OAuth Tokens section and click on Install to Organization.
Carefully copy and save the token values.

Add the ConductorOne app to all workspaces

in the Integrations section of the admin dashboard, click Installed Apps.
Locate the app you created. Click the … icon and select Add to more workspaces.
Check the box next to each workspaces you’d like to add the app to. To automatically add the app to new workspaces when they are created, check Default for future workspaces.
Click Next.
Check I’m ready to add this app.
Click Add App.

That’s it! Next, move on to the connector configuration instructions.

Configure the Slack Enterprise Grid connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Slack Enterprise Grid credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Slack Enterprise Grid and click Add.
Choose how to set up the new Slack Enterprise Grid connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Paste the user token into the User token field.
Paste the bot token into the Bot token field.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Slack Enterprise Grid connector is now pulling access data into ConductorOne.

Follow these instructions to use the Slack connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Slack Enterprise Grid connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Slack Enterprise Grid connector:
- Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
- Add the connector to a managed app (select from the list of existing managed apps)
- Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Slack Enterprise Grid connector deployment:

Secrets configuration

# baton-slack-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-slack-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

  # Slack Enterprise Grid credentials
  BATON_TOKEN: <Slack OAuth user token>
  BATON_ENTERPRISE_TOKEN: <Slack bot token>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-slack.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-slack
  labels:
    app: baton-slack
spec:
  selector:
    matchLabels:
      app: baton-slack
  template:
    metadata:
      labels:
        app: baton-slack
        baton: true
        baton-app: slack
    spec:
      containers:
        - name: baton-slack
          image: ghcr.io/conductorone/baton-slack:latest
          imagePullPolicy: IfNotPresent
          envFrom:
            - secretRef:
                name: baton-slack-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Slack Enterprise Grid connector to. Slack Enterprise Grid data should be found on the Entitlements and Accounts tabs.

That’s it! Your Slack Enterprise Grid connector is now pulling access data into ConductorOne.