> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/operate/customers/managing-customers.md).

# Manage customers

Create customers under Operate → Customers, scope API calls per customer, and monitor customer-level activity.

**Prerequisites:** [Your First Integration](https://docs.fastn.ai/get-started/quickstart.md).

Each company using your product is a customer. Each customer gets an isolated environment with their own connections, data, and execution history.

### Creating customers

1. Go to **Operate → Customers**.
2. Click **Create customer**.
3. Enter the customer details (name, and any other required fields). Optionally, put your own ID for this customer (for example `customer_12345`) in **External ID**; if you leave it empty, it defaults to the slug.
4. Click **Create Customer** at the bottom of the form. Note fastn's **customer id** or the External ID - you'll use one of them for API calls and widget embedding.

#### Which identifier to use

API calls and widget configuration identify a customer. Use fastn's customer id, or the External ID shown on the customer (your own id if you set one when creating the customer; otherwise it defaults to the slug). An identifier that matches neither returns 404 "Tenant not found".

{% hint style="info" %}
Pick one convention early. Changing identifiers later means updating every API call.
{% endhint %}

### Customer isolation

Every entity is scoped to a customer:

```
Your Organization
├── Customer A (Acme Corp)
│   ├── Connections: Acme's Shopify token, Acme's Slack token
│   ├── Executions: Only Acme's workflow runs
│   └── Data: Only Acme's orders, contacts, invoices
├── Customer B (Globex)
│   ├── Connections: Globex's HubSpot token
│   ├── Executions: Only Globex's workflow runs
│   └── Data: Only Globex's contacts
```

Workflows are defined once by you but execute per-customer using each customer's own connections and data.

### Customizing customer limits

By default, all customers share your plan's quota limits. To override limits for specific customers:

1. Go to **Settings → Billing**.
2. On the **Limits** card, click **Customize customer limits**.
3. Set per-customer overrides for any quota dimension.

Use this for:

* High-volume customers who need more events per day
* Trial customers with lower limits
* Enterprise customers with custom agreements

### Monitoring customer activity

#### Activity → Executions

1. Go to **Activity → Executions**.
2. Use the **"All workflows"** dropdown to filter.
3. Each execution row shows **Triggered by**, which tells you what started the execution: API key, Embed, Webhook, Schedule, Agent, Replay, Manual, or a person's name.

#### Activity → Events

1. Go to **Activity → Events**.
2. Filter by type: **All | Webhook | Scheduled | Manual**.
3. See incoming and outgoing events for your customers.

#### Audit log

For a complete history of all actions:

1. Go to **Settings → Audit log**.
2. Search by person, action or resource, and filter by person, action, resource type and date range.
3. Columns: Who, Action, Resource, Customer, Result, When.

### What you've learned

* How to create customers under Operate → Customers
* Customer isolation model i.e. each customer has separate connections, data, and executions
* How to customize quota limits per customer
* How to monitor customer activity through Executions, Events, and Audit log


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/operate/customers/managing-customers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
