LLMs.txt directory

AgentSpot administration

Learn the essential steps for an administrator to set up AgentSpot for their team.

Setting up AgentSpot

To set up AgentSpot, complete the following steps in order. Completing setup before adding end users ensures AgentSpot is ready for new users when they sign in for the first time.

  1. Set up roles and groups in ThoughtSpot: Create the roles and groups your users will need, but do not add end users to the groups yet. For details, see Managing users.

  2. Configure connectors in AgentSpot: Sign in to AgentSpot and enable the connectors your organization will use. For details, see Managing connectors.

  3. Set up org memory: Add your organization’s key facts and behavioral rules so that all agents and workflows share consistent context from the start. For details, see Org memory.

  4. Create and share agents: Set up agents and share them with your team so end users have a useful starting point. For details, see Creating an agent in AgentSpot.

  5. Add end users to their groups in ThoughtSpot: Once setup is complete, add users to the groups you created in step 1. For details, see Managing users.

Managing users

To add users to AgentSpot, you must do the following in your ThoughtSpot instance:

  1. Create a role with AgentSpot privileges.

  2. Add your role to a group.

  3. Add users to your group, as needed.

There are two primary AgentSpot privileges you can assign to a role:

Privilege Description

Can manage AgentSpot

Full administrative access to manage connectors, agents, and organization-wide settings

Can use AgentSpot

Access to AgentSpot to use shared agents
Users can only access AgentSpot after they have been assigned a role containing one of these privileges.

Creating a role with AgentSpot privileges

To create a role with AgentSpot privileges, do the following:

  1. Sign in to your ThoughtSpot instance.

  2. Go to the Admin tab.

  3. Under the Admin tab, click Roles.

  4. Click Create role.

  5. In the Create role window, enter a Role name and description.

  6. Click AgentSpot Control.

  7. Select one or more AgentSpot privileges for your role.

  8. Click Review selection.

  9. Review the role name, description, and admin controls.

  10. When you are ready to save your role, click Save.

  11. Create additional roles as needed.

Adding your role to a group

To add your role to a group, do the following:

  1. Under the Admin tab, click Groups.

  2. Click the More options more icon menu associated with the group and select Edit.

  3. In the Select roles section, select the checkbox for the role(s) you want to add and click Review selection.

  4. Review the roles you added and make changes, if needed.

  5. When you are ready to save your group, click Save.

Adding users to a group

When setting up AgentSpot for your organization, make sure you configure connectors, set up org memory, and create and share agents before adding end users to AgentSpot groups. For more information, see Setting up AgentSpot.

To add a user to a group, do the following:

  1. Under the Admin tab, click Users.

  2. Click the More options more icon menu associated with the user and select Edit.

  3. In the Edit user window, select the group which you want to add the user to and click Save.

After you set up your AgentSpot users, you are ready to log in to AgentSpot and add connectors. For details, see Managing connectors.

After users are added to a group with an AgentSpot privilege, they must refresh their browser while on the Insights tab of their ThoughtSpot instance before the AgentSpot option appears in the navigation.

Admin Settings

In the Admin Settings page you can view and manage the AgentSpot workspace. It is organized into the following sections:

  • Connectors: Manage connectors to different applications. See Managing connectors.

  • Slack bot: Enables two-way communication between Slack users and AgentSpot AI agents — without leaving Slack. See Slack bot.

  • Usage: View the overall usage of AgentSpot. See Monitoring usage.

  • Users: View details about AgentSpot users. See Monitoring users.

  • Audit log: View a chronological list of logged events. See Audit log.

  • Org memory: Add and manage the shared facts and rules that ground all agents and workflows in your organization. See Org memory.

Managing connectors

Connectors allow AgentSpot to interact with external applications like Jira, Slack, and Clay.

As an administrator, you have the authority to:

  • Add or remove connectors: for your entire organization.

  • Test before sharing: Activate a connector for yourself to verify it works before making it available to all users.

In the Admin Settings > Connectors page, you can see the list of Available Connectors. Once you add a connector, it appears in the list of Already Added connectors near the top of the page.

New connectors are added on a regular basis. Check the Admin Settings > Connectors page for the current list.

Requirements for adding a connector

  • You must know the URL of the MCP server for the external application you are connecting to. For details, refer to the documentation for the external application.

  • Your company must have a license for the external application.

  • You must have access to that external application.

Adding a connector

AgentSpot ships with native connectors for popular applications, listed under Available Connectors. If you want to connect to an external application that is not included, you can add it using a custom connector.

To add a connector, do the following:

  1. Sign in to AgentSpot.

  2. Click the Admin Settings 10 button in the upper-right corner.

  3. Under the Connectors tab, do either of the following:

    1. For an available connector: In the box for the connector, click Add.

    2. For a custom connector: Click + Custom Connector.

  4. In the Register window, do the following:

    1. For Connector Name, do either of the following:

      1. For an available connector (Optional): A name is already provided, but you can change it if you want.

      2. For a custom connector: Create a name for your connector.

    2. For Server URL, enter the connector’s MCP server URL. (Refer to the product’s documentation for that.)

    3. (Optional) For Transport Type, select either of the following:

      1. Streamable HTTP (Default and recommended)

      2. Server-Sent Events (SSE)

    4. (Optional) Enter a Description.

    5. (Optional) Choose an Authentication method.

    6. (Optional) Enter a Client ID (or leave it empty for auto-registration)

    7. (Optional) Enter a Client Secret (or leave it empty for PKCE flow)

    8. Click Register Connector.

Custom connectors

If an application is not in the list of available connectors, you can add it using a custom connector. Provide the URL for the MCP server and complete the setup to enable any compatible tool. Refer to the documentation for the product you want to connect for its MCP server URL.

User authentication and security

Connectors use each user’s existing credentials for the target application. When an admin enables a connector, each user must complete a one-time OAuth sign-in to authorize AgentSpot to act on their behalf. AgentSpot respects all existing permissions within the target app — users can only access data and perform actions they are already authorized to access in that application.

When an admin enables a connector (e.g., Jira), each user must log in with their individual credentials. AgentSpot respects all existing permissions within the target app; users will only see data and perform actions they are already authorized to access.

Slack bot

The AgentSpot Slack bot lets users interact with their agents from Slack. Once an admin connects a Slack app and binds a channel to an agent, anyone in that channel can @mention the bot and receive agent responses in the same thread.

Setup crosses back and forth between Slack and AgentSpot. The order matters, and AgentSpot states it directly on the page: use the event request URL in Slack, then verify the app before binding channels.

Here’s what it supports:

  • Interact with AI agents directly in Slack

    • @mention an agent in a Slack channel thread to ask it questions or trigger tasks

    • The agent processes your message and replies back in the same Slack thread

    • Works in public channels, private channels (with appropriate permissions), and direct messages (off by default, but the admin can opt-in).

Before you begin

  • You need permission to create and install a Slack app in your workspace. Scope changes may require workspace-admin approval.

  • You need admin access to AgentSpot (Admin Settings)

  • At least one agent must already exist, and be ready to bind.

  • Binding supports public channels only.

Part 1: Create the Slack app from a manifest

  1. Go to slack.com.

  2. Click the Your Apps button in the top right corner of the page.

  3. Sign into your Slack account if prompted.

  4. In the Slack API console, click Create New App, then choose From a manifest under "Or start your own way."

    slack bot new app
    From a manifest accepts JSON or YAML files.

Starting from a manifest sets the bot profile, scopes, and event subscriptions in one shot, which avoids the missing-scopes failure entirely.

Socket Mode hides the Request URL

This manifest ships with socket_mode_enabled: true. AgentSpot delivers events over an HTTP event request URL, and Slack hides the Request URL field in Event Subscriptions while Socket Mode is on. If you cannot find that field in Part 4, turn Socket Mode off under Settings > Socket Mode.

 
{
  "display_information": {
    "name": "agentspot-help",
    "description": "I help answer questions!~",
    "background_color": "#0d0e0f"
  },
  "features": {
    "app_home": {
      "home_tab_enabled": false,
      "messages_tab_enabled": true,
      "messages_tab_read_only_enabled": false
    },
    "bot_user": {
      "display_name": "agentspot-help",
      "always_online": true
    },
    "slash_commands": [
      {
        "command": "/agentspot-help",
        "description": "Get back a private answer!",
        "usage_hint": "Put your question here!",
        "should_escape": false
      }
    ]
  },
  "oauth_config": {
    "scopes": {
      "bot": [
        "app_mentions:read",
        "channels:history",
        "channels:join",
        "channels:read",
        "chat:write",
        "commands",
        "files:read",
        "files:write",
        "groups:history",
        "groups:read",
        "im:history",
        "im:read",
        "mpim:history",
        "reactions:write",
        "users:read.email",
        "users:read"
      ]
    },
    "pkce_enabled": false
  },
  "settings": {
    "event_subscriptions": {
      "bot_events": [
        "app_mention",
        "message.channels",
        "message.groups",
        "message.im",
        "message.mpim"
      ]
    },
    "interactivity": {
      "is_enabled": true
    },
    "org_deploy_enabled": false,
    "socket_mode_enabled": true,
    "token_rotation_enabled": false
  }
}

Rename agentspot-help and the slash command to suit the integration.

Part 2: Copy the credentials

As soon as the app is created and installed, Slack shows a " <app-name> is ready!" dialog with Your app credentials. This is the easiest place to grab the bot token. The eye icon reveals it, the copy icon copies it.

agentspot bot ready

Shown immediately after creating the app from a manifest. Copy the Bot token here.

  1. In the Your app credentials section, copy the Bot token and save it to a text file or other document.

    About the App token

    The xapp-…​ App token is generated because the manifest sets socket_mode_enabled: true. AgentSpot’s Admin UI does not ask for it. It only needs Bot token, Signing secret, and App ID. Ignore it unless you are building a Socket Mode app of your own.

  2. Go to Basic information > App Credentials and copy both App ID and Signing Secret and paste them into a text file or some other document. You’ll need to copy and paste each one in another step.

    Value Where in Slack Format

    Bot token

    "is ready!" dialog, or OAuth & Permissions > OAuth tokens

    xoxb-…​

    App ID

    Basic Information > App Credentials

    A…​

    Signing Secret

    Basic Information > App Credentials

    Hex string
    A Client Secret is not the Bot token.

    A Client Secret is a plain hex string and is the wrong value. The Bot token field rejects anything that is not a valid xoxb- token and save it in a text file or other document.

    If you dismiss that dialog, or need the token again later, go to OAuth & Permissions > OAuth Tokens:

    slack oauth permissions

    Any time you change scopes a yellow banner appears (as shown in the above image), prompting you to reinstall. You must reinstall your app before the token picks the scopes, and reinstalling reissues the token.

Part 3: Add the Slack app in AgentSpot

  1. In AgentSpot, go to Admin Settings > Slack bot and click +Add Slack app.

  2. Paste in the Slack app ID, Signing secret, and Bot token.

    Name in Slack API Name in AgentSpot admin settings

    App ID

    Slack app ID

    Signing Secret

    Signing secret

    Bot User OAuth Token

    Bot token
    add the slack app

    Admin Settings, Slack bot. New apps start as verification_failed with "Workspace not verified yet", This message remains until Parts 4 and 5 are done.

    Once saved, the app appears under Installed Slack Apps with a status badge, its App ID, and an Event request URL. The URL is unique per installation and follow this format:

    https://app.<tenant>.thoughtspot.cloud/api/v1/slack/tenants/<tenantId>/installations/<installationId>

Part 4: Paste the Event request URL into Slack

Copy the Event request URL from the app’s row, then in the Slack API console go to Event Subscriptions:

  1. Toggle Enable Events to on.

  2. Paste the Request URL and wait for Slack to show Verified. Copy it exactly, with no trailing white space. It must begin with https://.

  3. Under Subscribe to bot events, confirm app_mention is listed. The manifest adds it, but be sure to confirm it is listed.

If verification fails and the URL is definitely correct, then it is an endpoint issue. In that case, contact ThoughtSpot support.

Part 6: Invite the bot, then bind it to a channel

  1. In Slack, in the target channel run this command: /invite @your-bot-name

  2. Back in AgentSpot reload the Admin Settings > Slack bot page.

  3. Under Public Channel Bindings, do the following:

    1. Select the Slack app, the Agent, and the Public channel.

    2. Select the acknowledgement checkbox.

    3. Click Bind.

Part 7: Test

  • Mention the bot in the bound channel. The agent replies in the same thread.

    Test at the top level of the channel first rather than inside an existing thread. It rules out a whole class of ambiguity if something is wrong.

Required scopes

AgentSpot enforces a minimum set and names the missing ones in the error. The following are mandatory:

app_mentions:read, channels:read, users:read, users:read.email

The full manifest grants 16. Trim to least privilege for your actual flows, because excess scopes raise operational and security risk.

Purpose Scopes Needed when

Core mention and reply

app_mentions:read , chat:write

Always.

Channel listing and joining

channels:read , channels:join , channels:history

Always. channels:read populates the binding dropdown.

User identity

users:read , users:read.email

Always. Maps the Slack sender to an AgentSpot user.

Private channels

groups:history , groups:read

Not usable using this UI today.

Direct messages

im:history , im:read

Not usable using this UI today.

Group DMs

mpim:history

Not usable using this UI today.

Slash command

commands

Using /agentspot-help

Files

files:read , files:write

Agent handles file uploads or outputs.

Reactions

reactions:write

Bot acknowledges with emoji.

Troubleshooting

Every failure in this flow is silent. You get a disabled control or a generic status, never an explanation. These are the four, in the order that they occur.

Slack token is missing required Slack scopes

Adding scopes does not grant them to an existing token. Slack shows a yellow banner reading "You’ve changed the permission scopes your app uses. Please reinstall your app for these changes to take effect."

  1. Open OAuth & Permissions > Bot Token Scopes and confirm the scopes are under Bot, rather than User. They are two separate columns.

  2. Click Reinstall to <workspace>.

  3. Copy the new Bot User OAuth Token. Reinstalling reissues it, so the one in AgentSpot is now stale.

  4. Update the Bot token in AgentSpot, save, then click Verify again.

Bot is bound but never replies

When the bot is bound but never replies, it can be caused by any of the following:

  • The signing secret is incorrect.

  • Socket mode is enabled.

  • Event Subscriptions are not enabled.

  • The Slack API needs to be reinstalled.

Recommended next steps:

  1. Make sure the signing secret is correct. AgentSpot signature-verifies every inbound event, so a stale or mistyped signing secret means events arrive and are silently rejected. This produces exactly this symptom. For details, see Part 2: Copy the credentials.

  2. Make sure Socket Mode is disabled, see Part 1: Create the Slack app from a manifest.

  3. Make sure Event Subscriptions is enabled, the URL shows Verified, and app_mention is subscribed. If there is no Request URL field at all, Socket Mode is still on.

  4. If the app was reinstalled after adding the event, Event subscriptions in Slack must be reinstalled.

  5. The Slack email matches the AgentSpot email. That is what users:read.email is for. An unmatched sender is dropped.

  6. The user has agent access. Slack does not widen access. Only users who already have the agent in AgentSpot can trigger it.

In AgentSpot use Admin Settings > Audit log to split the problem. If nothing is logged it means Slack is not sending, so check causes 1 and 2. Logged but no run means AgentSpot is rejecting, so check causes 3 through 5.

Binding overwrites an existing one

Channel to agent mapping is 1:1. Binding a channel that is already bound replaces the previous agent. This is why binding is admin-only.

Monitoring usage

The Usage page provides high-level analytics to help you track the ROI and adoption of AgentSpot.

You can monitor the following:

  • Total active users

  • Number of conversations

  • Connector usage frequency

Monitoring users

The Users page allows you to view detailed information about users and groups who use AgentSpot.

It provides the following information:

  • Users: Number of total users

    • Name

    • Email address

    • Role: Member or Admin

You can download a .csv file containing a complete list of AgentSpot users, including User ID, Name, Email, and Role by clicking 10 Export.

To add or remove Age ntSpot users, you must go to the Admin Settings > Users tab in your ThoughtSpot instance.

Audit log

The audit log page displays a chronological list of logged events, most recent first.

Each entry shows:

  • Time: Month, day, year and time (based on user’s timezone?)

  • Actor: Firstname, lastname, and email address of the user

  • Action: Specific action performed (link to full reference to provide more detail)

  • Resource: Which resource was used (which tool call)

  • IP: IP address of user

Filtering the audit log

You can filter the audit log by a specific action, actor user ID, and a date range.

You can download a .csv file of the audit log by clicking 10 Export. If you filter the audit log before downloading it, the downloaded file will only include your filtered version.

Org memory

Org memory is the shared set of facts and behavioral rules that AgentSpot applies across all agents and workflows in your organization. Setting up org memory early in the setup process ensures that every agent your team builds or uses starts with accurate, consistent organizational context — without each agent needing to be individually configured with the same information.

Seed org memory before creating agents or adding end users. Agents built on top of a well-configured org memory require less individual instruction and behave more consistently across your organization.

Facts vs. rules

Org memory is organized into two types of entries:

Type Think of it as…​ Description

Facts

Grounding truths

Static information about your organization that agents use as reliable context. Facts help agents reason correctly when they encounter numbers, names, or terms that should match known values. For example, if an agent retrieves a revenue figure that does not match the fact you provided, it will flag the discrepancy and ask for clarification.

Rules

Behavioral recipes

Instructions that agents follow when generating responses. Rules define how agents should behave in specific situations — including boundaries, approval steps, and standard operating procedures. For example, a rule might specify that outbound customer emails require human approval before being sent, or define the steps your organization follows for competitive intelligence research.

What to include in org memory

The following table lists the categories of information that are most valuable to include.

Category Examples

Company basics

Company name, legal name, industry, headquarters locations

Financial context

Annual revenue, fiscal year start date, quarter definitions

Products and services

Product names, descriptions, and which ThoughtSpot data models are associated with each

Key metrics and acronyms

Definitions for internal metrics, abbreviations, and terminology used across teams

Technology stack

Names of key tools, platforms, and systems in use

Rules and procedures

Standard operating procedures, approval requirements, and behavioral boundaries for agents (for example, "Exclude test accounts from all reports" or "Outbound customer emails require human approval before sending")

Adding org memory

To add facts and rules to org memory, do the following:

  1. Sign in to AgentSpot.

  2. Click the Admin Settings 10 icon in the upper-right corner.

  3. Select the Org memory tab.

  4. Click Add fact or Add rule, depending on the type of entry you are adding.

  5. Enter your content.

    Org memory entries support markdown formatting. You can use tables, lists, and headings to organize content within a single entry.

  6. Click Save.

  7. Repeat for each fact or rule you want to add.

After saving, org memory is broken down into sections in the UI. You can review, edit, and correct individual entries at any time by clicking directly into them.

Updating org memory over time

Org memory is not a one-time configuration. As your organization evolves, you can update facts and rules directly in the UI.

In addition, as administrators use AgentSpot, memories can be extracted from agent conversations and added to org memory.

Managing agents

As an administrator, you have full visibility over all agents and workflows created within your organization, regardless of who owns them. You can share agents with teams, and if a user leaves the company, you can manage, edit, or reassign their agents and workflows.

View agents in your organization

To see all agents in your organization do the following:

  1. From the AgentSpot homepage, under My Team, click Browse existing agents.

  2. Click From My Org.

Share an agent in your organization

To share an agent in your organization, do the following:

  1. From the AgentSpot homepage, click the agent you want to share.

  2. In the upper-right corner of the agent window, click Share agent.

  3. In the Share window, do the following:

    1. In the Add people or groups field, find the people or group(s) to share with.

    2. In the Ready to share field, confirm the people or group(s) to share with.

      1. For each person or group added, using the menu on the right to specify whether they Can use or Can edit the agent.

    3. In the People and groups with access field, confirm the people and groups who already access and make changes, if needed.

    4. Click Done.

      The agent you shared will now appear in the Agents dashboard for the people and groups you shared it with.