Set up a Slack connector

Yes, there are TWO kinds of Slack integration! The instructions below connect a Slack Pro or Business+ workspace with ConductorOne so that you can review access data and grant user access to Slack.(We also have an connector for Slack Enterprise Grid 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

Slack Pro

Resource	Sync	Provision
Accounts
Workspaces
Workspace roles
Groups

A limitation in the Slack APIs means that automatic account provisioning is not currently supported for Slack Pro workspaces.

Slack Business+

Resource	Sync	Provision
Accounts
Workspaces
Workspace roles
Business+ roles
Groups
IDP groups*

*The connector can sync and provision IdP groups only if SSO is configured for your Slack Business+ instance. IDP group provisioning is not supported for GovSlack instances. A limitation in the Slack APIs means that automatic account provisioning is not currently supported for Slack Business+ workspaces.

Gather Slack credentials

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

A user with the Admin role in the Slack workspace must perform this task.

Step 1: Generate a Slack app-level token

Make sure you are signed into Slack, then navigate to api.slack.com/apps/.

Click Create an App and select the From scratch option.

Give your new Slack app a name, such as “ConductorOne integration”, and select the workspace you want to integrate with ConductorOne.

Click Create App.

Your new app opens. From the menu on the left, select OAuth & Permissions.

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
userprofile:read
users:read
users:read.email

Business+ users only: 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 (only include if you have SSO enabled and want ConductorOne to provision IDP groups)

Scroll up to the top of the page. In the OAuth Tokens for Your Workspace area, click Install to Workspace.

When prompted, allow your new app to access the Slack workspace.

Your user OAuth token is created. Copy and save the token value.

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

Configure the Slack connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Slack credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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 and click Add.

Choose how to set up the new Slack 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.

Business+ users only: Paste the token into the Business plus token field.

If you’re using a GovSlack instance, click the checkmark to Enable GovSlack.

Pro users only: Paste the token into the Access 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 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 connector

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Slack 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

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 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>
  
  BATON_TOKEN: <Slack OAuth token for a Pro workspace>
  BATON_BUSINESS_PLUS_TOKEN: <Slack OAuth token for a Business+ workspace>

  # Optional: include if SSO is enabled on yous Slack instance 
  BATON_SSO_ENABLED: true

  # Optional: include if you're using a GovSlack instance
  BATON_GOV_ENV: 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
        env:
        - name: BATON_HOST_ID
          value: baton-slack
        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 connector to. Slack data should be found on the Entitlements and Accounts tabs.

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

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Capabilities

Slack Pro

Slack Business+

Gather Slack credentials

Step 1: Generate a Slack app-level token

Configure the Slack connector

Step 1: Set up a new Slack connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Slack Pro

​Slack Business+

​Gather Slack credentials

​Step 1: Generate a Slack app-level token

​Configure the Slack connector

​Step 1: Set up a new Slack connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Slack Pro

Slack Business+

Gather Slack credentials

Step 1: Generate a Slack app-level token

Configure the Slack connector

Step 1: Set up a new Slack connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector