Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/credit-budgets.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ A **budget** is a named credit pool with:

When a workbook (or other resource) is assigned to a budget, all credit-consuming actions in that resource count against the budget's balance. If a budget runs out of credits, processing in assigned resources stops until an admin increases the limit or resets the spend.

**Note:** The Budgets tab in `Settings` → `Usage` shows credit spend aggregated by budget — it does not break down spend by individual user within the budget. To see which specific Sales Rep or MCP user consumed credits, use the **MCP** tab in `Settings` → `Usage`, which shows per-user spend for anyone accessing Clay through Claude, ChatGPT, or Glean. To set or adjust individual credit limits for those users, see [MCP settings](https://university.clay.com/docs/mcp-settings).

## Creating a budget

1. Go to `Settings` → `Budgets`.
Expand Down
4 changes: 4 additions & 0 deletions docs/mcp-settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,10 @@ If this happens: have the rep disconnect Clay in their AI tool (remove and re-ad

For a full breakdown of all roles, see [Roles and permissions](https://university.clay.com/docs/roles-and-permissions).

### Can I disable Clay Sequencer access for Sales Rep users?

No. The Sales Rep role bundles MCP access (invoking Clay through Claude, ChatGPT, or Glean) and Sequencer email account setup together — there is no way to enable MCP access without also allowing the rep to set up email accounts in the Clay Sequencer. If you need to remove Sequencer access for a specific rep, remove them from the workspace entirely (`Settings` → `Team` → three-dot menu → `Remove member`).

### Does MCP work with SSO-enabled workspaces?

Yes. Workspace membership is the access gate for MCP — SSO determines how users authenticate, not whether they can access MCP. Users on an SSO-enabled workspace must still be explicitly added to your Clay workspace via `Settings` → `Team` → `+ Invite` before they can use Clay through Claude, ChatGPT, or Glean. SSO does not automatically grant workspace access.
Expand Down