What you need. An Axia Security administrator account (the Connect screen is for administrators), and permission in Slack to create and install apps in your workspace.
Where to start. Open Slack on the Connect screen. The same steps are shown there, above the credential fields.
What Axia Security does in Slack
Axia Security reads the messages in the Slack channels you add its app to, and the files shared there, including their content — nothing else. It does not read direct messages or any other channel.
Axia Security never posts, reacts or changes anything in Slack.
Reading starts once you finish the two steps shown after you connect: Slack checks the address Axia Security receives events at, and you add the app to a channel. It stops when you remove the Slack connection on the Connect screen.
Why the app asks for each permission
The manifest asks for these seven read permissions and nothing else. Connect checks that the app has each of them.
| Permission | Why |
|---|---|
channels:history | Reading messages in the public channels the Axia Security bot was added to |
groups:history | Reading messages in the private channels the Axia Security bot was added to |
channels:read | Reading the name and sharing of the public channels the bot is in |
groups:read | Reading the name and sharing of the private channels the bot is in |
users:read | Telling members, guests and people from outside the organization apart |
users:read.email | Reading each author's email address, to match them to the employee directory |
files:read | Reading the files shared in those channels, including their content |
Set up the Axia Security app in Slack
1. Copy the Axia Security app manifest
On the Connect screen, select Copy manifest. If your browser does not allow copying, select Download manifest and open the file in a text editor. Keep the Connect window open: after you create the app in Slack, you come back to it to paste two values from the app.
2. Start a new app in Slack
Open api.slack.com/apps in a new tab, sign in to your Slack workspace if Slack asks, and select Create an App.
3. Create the app from the manifest
Select From a manifest, then Continue. On the next screen choose the YAML tab, delete the example text, paste the manifest you copied in step 1, choose your workspace and select Next.
4. Install the app in your workspace
Slack shows a summary of the app. Select Create and Install, then Allow if Slack asks.
5. Open the app's settings
Slack shows “Axia Security is ready!” with Slack CLI steps. You don't need them: select Go to App Settings. Keep this Slack tab open.
6. Copy the Signing Secret
In the app's settings, select Basic Information in the left menu. Under App Credentials, next to Signing Secret, select Show, then copy the value. Copy the Signing Secret, not the Client Secret or the Verification Token beside it.
7. Paste the Signing Secret on the Connect screen
Come back to the Connect window and paste it into the Signing Secret field at the bottom.
8. Copy the Bot User OAuth Token
In the Slack tab, select OAuth & Permissions in the left menu. Under OAuth Tokens, next to Bot User OAuth Token (it starts with xoxb-), select Copy.
9. Paste the token on the Connect screen and connect
Come back to the Connect window, paste it into the Bot User OAuth Token field at the bottom and select Test & Connect. The two steps left then appear on the Connect screen.
Axia Security checks the token with Slack and checks that the app has every permission listed above. If a permission is missing, Connect names it (see If something does not work).
You paste both values directly on the Connect screen; nobody needs to send them to Axia Security by email.
Finish in Slack
After Test & Connect, the Connect screen says: "Slack is connected. Reading starts once you finish steps 10 and 11 in Slack." It then shows steps 10 and 11 and the list Slack channels Axia Security reads.
10. Verify the events address in Slack
In the Slack tab, select Event Subscriptions in the left menu. The Request URL may first show “Your URL didn't respond”: that is expected (Slack tried it before Axia Security had your secret). Select Retry (or Verify); it turns Verified. Then select Save Changes at the bottom of the page.
11. Add the Axia Security app to each channel it should read
In the channel, type /invite @Axia and choose Axia Security from the list that appears (public and private channels alike). Or open the channel's details → Integrations (in newer Slack: Agents & apps) → Add an app → Axia Security. You need permission to invite people in that channel; if Slack says you don't have it, ask the channel's manager or a workspace admin, or use a channel you created. Axia Security reads exactly the channels the app is in; remove it from a channel to stop.
On the Connect screen, select Done when you have finished. The list Slack channels Axia Security reads is an optional check: it shows what Slack says the app is in right now, and marks channels that are Private or Shared with another organization. Select Refresh after you add the app to a channel.
If something does not work
Connect says "Missing required permissions"
The app in Slack does not have every permission Axia Security reads with; Connect names each one that is missing. In your app's settings, open OAuth & Permissions → Scopes and add each permission named. Reinstall the app to your workspace, then select Test & Connect again.
Slack says "Your URL didn't respond"
Slack tried the Request URL before Axia Security had your Signing Secret, which is expected the first time. Select Retry next to the Request URL; once it shows Verified, select Save Changes. If it still does not respond, the most common reason is that the secret pasted on the Connect screen is the Client Secret or the Verification Token instead of the Signing Secret: on the Connect screen select Manage on the Slack card, paste the Signing Secret from Basic Information → App Credentials again and select Save changes, then select Retry in Slack. If it still does not turn Verified, contact Support.
Slack says "You don't have permission to invite people to this channel"
Adding the app to a channel needs permission to invite people to that channel. Ask the channel's manager or a workspace admin to add the Axia Security app there, or use a channel you created.
The Slack card says "Awaiting first event"
The connection is saved, but no message has reached Axia Security yet. Check that the Request URL shows Verified (step 10) and that the app is in at least one channel (step 11). It clears when the first message arrives in a channel the app is in.
The Slack card says "No messages for 24 h"
No message has reached Axia Security from the workspace in the last 24 hours. A quiet channel or a weekend can cause it. Check that the app is still in the channels Axia Security should read and that the Request URL still shows Verified. It clears when the next message arrives.
Verification checklist
- The app is created from the Axia Security manifest and installed to your workspace (Create and Install).
- The Signing Secret (not the Client Secret) and the Bot User OAuth Token (
xoxb-) are pasted, and Test & Connect succeeded. - The Request URL shows Verified under Event Subscriptions, and you selected Save Changes.
- The Axia Security app is in each channel Axia Security should read, and those channels appear under Slack channels Axia Security reads.
- After the first message in one of those channels, the Slack card no longer says Awaiting first event.