Skip to main content

Prerequisites

  • A Microsoft 365 tenant with Teams enabled
  • Admin consent permissions (Global Admin or Teams Admin)

Installation

  1. Go to app.nextks.com/signin
  2. Click Add to Microsoft Teams
  3. You’ll be redirected to Microsoft’s admin consent page
  4. Sign in with your admin account and grant the requested permissions
  5. 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. The admin consent authorizes NextKS for your entire Microsoft 365 tenant.

What NextKS needs access to

PermissionPurpose
Send and receive messagesDeliver notifications and process user input
Create conversationsOpen DM channels with users for notification delivery
Read user profileMatch users by email for notification routing

Signing in (after installation)

Once the workspace is connected, team members sign in at app.nextks.com/login:
  1. Click Sign in with Microsoft Teams
  2. Authorize the sign-in in the Microsoft 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

After installation, team members can:
  • Search for “NextKS” in the Teams app bar and start a chat
  • Receive notifications as DMs from the bot
  • Click Adaptive Card buttons on interactive notifications

Adding team members

Users are registered when they first sign in, message the bot, or receive a notification via the API. The bot matches users by their Microsoft 365 email address.

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

  • Admin consent may take a few minutes to propagate
  • Verify the consent was completed successfully in Admin Settings
  • Check that your Teams admin hasn’t blocked third-party apps
  • Ensure the recipient’s email matches their Microsoft 365 account email
  • The bot needs to create a conversation first — this requires correct tenant configuration
  • Try reconnecting from Admin Settings if the issue persists
  • Adaptive Card interactions require the bot to have correct messaging permissions
  • Try reconnecting the app from Admin Settings in the dashboard