Skip to main content

Prerequisites

  • A Slack workspace where you have admin permissions

Installation

  1. Go to app.nextks.com/signin
  2. Click Add to Slack
  3. Review the requested permissions in the Slack OAuth prompt and click Allow
  4. You’ll be signed in to the NextKS dashboard automatically as the organization admin
The installation process creates your NextKS organization and signs you in — no separate account creation needed.

What NextKS needs access to

PermissionPurpose
Send messages as botDeliver notifications and AI responses
Read messages in DMsProcess user messages to the bot
Manage interactive messagesHandle button clicks and responses
NextKS only reads messages sent directly to the bot — it does not access channel conversations.

Signing in (after installation)

Once the workspace is connected, team members sign in at app.nextks.com/login:
  1. Click Sign in with Slack
  2. Authorize the sign-in in the Slack OAuth prompt
  3. You’re signed in to the NextKS dashboard
New users are created with the member role. The original installer is the admin.

Using the bot

Team members can:
  • DM the NextKS bot to interact with configured MCP servers
  • Receive notifications sent via the API as DMs from the bot
  • Click response buttons on interactive notifications

Adding team members

Users are automatically registered when they first sign in, message the bot, or receive a notification. No manual user provisioning is required.

Reconnecting

If you need to update the bot token (e.g., after revoking permissions), an admin can reconnect from Admin Settings in the dashboard.

Troubleshooting

  • Verify the bot is installed: check Apps in your Slack sidebar
  • Ensure the workspace admin hasn’t restricted bot access
  • Check the NextKS dashboard Admin Settings for connection status
  • Verify the recipient’s email matches their Slack profile email
  • Check that the API key belongs to the correct organization
  • Review the API response for specific error messages
  • Interactive features require the Slack app to have the correct scopes
  • Try reconnecting the app from Admin Settings in the dashboard