There are a few extra requirements, steps and considerations when you're developing on an Enterprise Grid organization.
While we'll discuss a few special privileges provided to those powerful Org Admins, the following material is recommended reading for all developers on an Enterprise Grid organization.
This guide will use the following terms:
team.For example, imagine there is a Kingdom of Britain organization. King Arthur is one of its Org Admins. This organization contains the Knights of the Round Table workspace, of which King Arthur is a member, along with other users such as Mordred and Lancelot.
With the terms defined, here's what Org Admins and developers need to know about the Slack CLI.
Any developer using the Slack CLI in an organization will need to use v2.9.0 or later of Slack CLI.
Keeping your version of the Slack CLI up-to-date is recommended for a bevy of reasons. The Slack CLI will also prompt you to update.
If you're not sure if you're on a recent enough version, you can check with the following command:
slack --version
If you're experiencing login errors, try checking what version of the Slack CLI you're using! You won't be able to log in to an organization on earlier versions of the Slack CLI.
Developers log in with the Slack CLI tool to their entire organization.
The login steps are the same as any other user, whether you are an Org Admin or not. Use the slack login command and paste the /slackauthticket <your auth ticket> in any Slack channel or DM. Doing so will log you into the entire organization.
You can confirm this is the case with the slack auth list command. You'll get the following output:
OrgName (Team ID: E123ABC456)
User ID: U123ABC456
Last Updated: 2023-12-31 23:59:59 -7:00
Authorization Level: Organization
Since you're logged in to your organization, the apps you create will belong to your organization.
Prior to Slack CLI v2.9.0, the Slack CLI was not compatible with an entire Enterprise Grid. Developers could, however, log in to a workspace of their organization. A developer who was developing with the Slack CLI prior to v2.9.0 may still show the following output from slack auth list:
WorkspaceName (Team ID: T123ABC456)
User ID: U123ABC456
Last Updated: 2023-12-31 23:59:59 -7:00
Authorization Level: Workspace
This legacy workspace-specific level authorization will still work, but is no longer grantable to new developers. If you log out or invalidate your login, you'll log in again with an organization level authorization.
Apps created with a legacy workspace-level authorization can still be managed by app owners or app collaborators with organization-level authorization, provided the workspace belongs to the organization.
By default, Admin Approval of Apps is turned on for all Slack Enterprise Grid organizations.
Here's what the request flow looks like when trying to install an app to an organization:
If your organization turned Admin Approval of Apps off, then no approval is needed. The first attempt to install your app should succeed.
While workflow apps are installed on an entire organization, they do not necessarily have access to every workspace in the organization.
Granting access to workspaces is done when an app is run on a local development server or deployed to production. The Slack CLI will prompt you to select whether to install with access to a single workspace or all workspaces in an organization.
You can also skip the prompt and proactively grant the desired access by appending -org-workspace-grant <team_id> to the relevant command.
For running on a local development server:
slack run -org-workspace-grant <team_id>
For deploying to production:
slack deploy -org-workspace-grant <team_id>
Org Admins can adjust an app's access grants anytime after granting their approval. Admins can change what workspaces the app has access to via Administration Settings. From there:
Use this process to ensure only desired apps are available in the proper workspaces.