> 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/get-started/onboarding/setting-up-your-organization.md).

# Set up your organization

Configure your organization profile, team access, customers, plan limits and audit log after your first fastn login.

Onboarding (at `/onboarding`) takes you through four steps: **Connect your product**, **Choose integrations**, **Embed the widget** and **Customers connect and customize**. Alongside it, a handful of organization-level settings control your company profile, team access, customer management and billing. This tutorial walks through each one.

### Step 1: Configure organization settings

1. Click **Settings**, the last item in the left sidebar.
2. Click **General**.

The **Organization** card holds:

**Name** - How your company appears across the platform.

**Timezone** - Sets the default timezone for new schedules. Dates elsewhere are shown in each viewer's own timezone.

The **Joining by email domain** card lets people sign up and ask to join instead of waiting for an invite:

* **Email domain** - Your company's domain (for example `yourcompany.com`). It has to be a domain your organization controls, not a mailbox provider.
* **Approve automatically** - Off means an admin has to approve each request. Leave it off unless the domain is yours alone.
* **Role people joining on this domain get** - The starting role for people who join through the domain. It also preselects the role when you invite someone on that domain.

### Step 2: Invite your team

1. Go to **Settings → People**.
2. Click **Invite someone**.
3. Enter their email address.
4. Select a role.
5. Send the invite. They'll receive an email to join.

The People page shows a table with columns **Person**, **Role**, **Status**, **Added** and **Access** (Access shows when a time-limited grant ends).

#### Roles

fastn has these system roles. **Settings → Roles** counts each role's permissions across 11 resources (Connectors, Connections, Workflows, Users, Settings, Events, Secrets, Executions, Widgets, Customers and Unified API), 44 permissions in all:

| Role          | Permissions | What they can do                                                                                                                                              |
| ------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**     | 44          | Everything an Admin can do, plus managing admins and transferring ownership. One per organization.                                                            |
| **Admin**     | 44          | Full access within the organization and its customers: connectors, workflows, customers, billing, settings.                                                   |
| **Developer** | 36          | Builds and deploys connectors and workflows, and uses Build with AI. No billing, people management or audit log.                                              |
| **Operator**  | 21          | Configures connections and runs workflows. Deploys to test only.                                                                                              |
| **Viewer**    | 6           | Read-only access to connectors, connections, workflows, widgets, events and the Unified API. Not executions, users, settings or secrets, and no AI assistant. |
| **End User**  | 35          | The role for people at your customers using the embedded widget: create connections and use the widget's assistant inside their own customer.                 |

To see the full permission breakdown or build your own role, go to **Settings → Roles** and click **Create custom role**. A custom role is based on a system role and can't go beyond it.

### Step 3: Manage customers

Your customers (the companies using your product, who turn on integrations in your widget) are managed under:

1. Go to **Operate → Customers**.
2. The page reads: "Every customer using your embedded integrations. Your widget is what they see; this is where you watch each one's installs and connections."

Each customer is isolated: its own connections, data, sync history and configuration. Your backend registers each customer, and its connections show up once it connects an app in the widget.

From this page you can view customer details and monitor their integrations. Per-customer limit overrides are set from Billing (Step 4).

### Step 4: Check your plan and limits

1. Go to **Settings → Billing**.
2. At the top is your plan: its name and price, with **See plans** (on Launch) or **Request plan change**.
3. The **Limits** card lists each limit with its name, a usage bar, used against the cap, and the percentage used. For most limits, going over stops new work rather than charging you, and nothing already running is interrupted. The exception is customer connections on Scale: past the 10 included, each extra one is billed rather than refused.

Key limits on the **Launch** plan:

| Limit                                                                                 | Default on Launch |
| ------------------------------------------------------------------------------------- | ----------------- |
| Events per day                                                                        | 500               |
| API calls per day                                                                     | 1,000             |
| API requests per minute (a rate limit per organization, not shown on the Limits card) | 100               |

There is no events-per-minute cap on Launch unless an admin sets one.

Click **Customize customer limits** on the Limits card to set per-customer overrides. Overrides win over the plan default, which is useful when specific customers need higher limits, or when you want to throttle individual customers to protect shared capacity.

### Step 5: Review the Audit log

1. Go to **Settings → Audit log**.
2. The log shows a table with columns **Who**, **Action**, **Resource**, **Customer**, **Result** and **When**.

Significant actions in your organization are recorded here, from workflow deployments and connector changes to customer connections. Use it for compliance, debugging, or understanding who changed what. The audit log is for Owners and Admins.

### For your development team

A few places your developers will need:

* **API keys** - Under **Embed → API keys and MCP → API keys**: Test and Live keys for programmatic access to the fastn API, including the key your backend uses to mint embed tokens.
* **Secrets** - Under **Settings → Secrets**: sensitive values (third-party tokens, database credentials) that workflows read at runtime.
* **Environments** - Under **Settings → Environments**: where published workflow versions are deployed, such as test, live and your own named ones.
* **Your own OAuth apps** - fastn manages OAuth apps for many common platforms. To use your own OAuth application for a connector instead, set it on that connector's **Auth** tab.

See the [Developer](https://docs.fastn.ai/reference/tutorials/developer.md) tutorials for the full setup guide.

### What you've configured

* Organization name, timezone, and joining by email domain
* Team members invited with appropriate roles
* Customer management set up
* Plan limits reviewed, with per-customer overrides where needed
* Audit log available for compliance and debugging
* Developer team pointed to API keys, Secrets, Environments and connector auth


---

# 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/get-started/onboarding/setting-up-your-organization.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.
