> ## Documentation Index > Fetch the complete documentation index at: https://agentheya.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Subscribers > Manage subscribers who use and build on your agent. The Users page shows every subscriber who has registered for — or was granted — access to your agent. From here you can create direct logins, invite users by email, set each user's recurring credit budget, view per-user usage and subscription state, top up credits, suspend or block accounts, review bot-detection events, and delete users. ## Adding users Two buttons sit at the top of the page: * **Create User** — creates an active web login immediately. Enter the user's email and a password (you set it; a minimum length is enforced) — **no email is sent**. The user can sign in with those credentials right away. * **Invite Users** — opens the invite dialog. Paste one or many emails (one per line; commas also work) or upload a CSV file (one email per line, first column is used). Up to **100 emails per batch** are accepted. Each address receives an email with a sign-up link pre-scoped to your agent; an address that already exists but hasn't completed its invite gets a fresh token. Results are summarised by status: `Sent`, `Re-invited`, `Already had access`, `Invalid email`, `Failed`. Both dialogs include the recurring **budget selector** described below. ## Budgets The budget selector appears in **Create User**, **Invite Users**, and the per-row **Edit budget** action. It sets a user's spending allowance in one of two mutually exclusive modes: * **Credit budget** — a credit amount plus a refresh cadence: **One-time (no refresh)**, **Per day**, **Per week**, or **Per month**. The user gets free access with that recurring allowance. * **Must select a paid plan** — the user must subscribe to one of your paid plans before they can use the agent. Available to **Business**-plan owners only. Editing a budget via **Edit budget** refills the user's balance immediately and restarts the refresh cycle from today. ## User list The table shows one row per registered subscriber, with columns for: | Column | Description | | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | **Name** | Display name (defaults to the email if no name was set). | | **Email** | Login email. | | **Sign-in** | One badge per authentication method on the account — `Email` (password) plus any linked SSO providers. | | **Role** | The user's role (e.g. `user`). A second green badge appears if the person also has dashboard access via Team & Roles. | | **Registered** | Date the account was created. | | **Last Login** | Date of the most recent login. | | **Status** | `Active`, `Invited` (account exists but the invite link hasn't been completed), `Suspended`, or `Blocked`. | | **Credits Left** | Current credit balance. | | **Budget** | The recurring allowance — e.g. `500 / month`, `100 one-time`, or `Paid plan`; `—` when none is set. | | **Next Reset** | When the recurring credit budget next refreshes. | | **Used (Month)** | Credits consumed in the current billing month. | | **Used (Total)** | Credits consumed lifetime. | | **Plan** / **Cost/mo** / **Credits/mo** | Subscription plan, monthly cost, and monthly credit allotment. | | **Actions** | Three-dot menu (see below). | ## Row actions Click the three-dot menu on any row to open the actions popup: * **View in Stripe** — opens this user's customer page in the Stripe dashboard (only shown when a Stripe customer ID is on file). * **Edit budget** — reopens the budget selector to change the user's recurring credit budget or switch them to a paid plan. Refills the balance and restarts the cycle immediately. * **Set credits** — a one-off manual override: type a new credit balance (zero or greater). Useful for compensating users after service issues or for handing out promotional credit. * **Resend invite** — shown only for users in the `Invited` state; sends a fresh invite link. * **Suspend / Unsuspend** — suspending signs the user out immediately and blocks them from logging in until unsuspended (optional reason). Unsuspend from the same menu. * **Block / Unblock** — blocking removes the account's access to this agent (optional reason); blocked users see an "access suspended" message. Unblock from the same menu. * **View bot events** — appears only when bot-detection events are on file for the user; opens the **Bot Detection Events** panel (see below). * **Delete** — permanently removes the account. This cannot be undone. **Suspend** signs the user out and prevents further login until you unsuspend them; **Block** leaves the login intact but denies the account access to this agent. Both accept an optional reason. ## Bot detection events The platform records automated-abuse signals against a user when its bot-detection traps fire. Whenever any events exist for a user, a **View bot events** action appears in their three-dot menu and opens the **Bot Detection Events** panel. Each entry is either a honeypot trap trigger (**Trap sprung**) or an enforced ban (**Ban enforced**), shown with a timestamp and details such as the user agent, elapsed time since the trap was set, interaction count, and the agent involved. ## Subscription tiers Each user's plan, monthly cost, and monthly credit allotment are displayed in the row but managed via the **Pricing** page and the user's own subscription flow. Use **Set credits** for direct manual adjustments. ## What subscribers can configure themselves Each subscriber gets their **own** limited dashboard at `/agent//dashboard`, mirroring your owner editors but **scoped to that single subscriber** — their data, connected accounts, schedules, and settings are isolated per user and never affect your configuration or anyone else's. Which pages they see is **controlled by their pricing tier**: a page appears only if the tier the subscriber is on includes it. Independent of tier, every subscriber always has their own **Memory**, **Inbox / Emails**, **Activity**, and **Profile**. Tier-gated pages an owner can grant include Rules, Examples, Data, Widgets, Schedules, IM Channels, Email Addresses, API Keys, Webhooks, Handoff, Connectors, Tools, Hooks, and Feeds — all scoped to the individual subscriber. See [Pricing](/sidebar-menu/pricing) to set which tier unlocks what. ## In practice **Onboard a cohort.** You're rolling the agent out to a team of 40. Click **Invite Users**, paste or upload their emails (up to 100 per batch), set a monthly credit budget, and send. Everyone gets a sign-up link pre-scoped to your agent; the results summary tells you which were sent, which already had access, and which addresses were invalid. **Hand someone a direct login.** For a demo account or an internal user you'd rather not email, click **Create User**, enter their address and a password, and set a credit budget. They can sign in immediately — no invite round-trip. **Compensate after an incident.** A user hit an outage and burned credits on failed queries. Open their three-dot menu → **Set credits** and bump their balance to make them whole. Use the same action to hand out promotional credit to a trial user you want to convert. **Cut off abuse.** A user is hammering the agent or violating your terms. Check **View bot events** to confirm what tripped, then **Suspend** them (signs them out and blocks login) or **Block** them (denies access to this agent) with a reason — reversible from the same menu if it was a mistake. ## Manage via the Management MCP This area is managed through the [Management MCP](/manage-mcp) at `https://manage.agentheya.com/mcp`. | | | | -------- | ------------------------------------------------------- | | Endpoint | `https://manage.agentheya.com/mcp` | | Tools | `list_power_users, get_power_user, set_power_user_tier` | All tools take `owner_id` + `agent_id` as required arguments. See the [Management MCP guide](/manage-mcp) for authentication and the full tool catalogue.