> For the complete documentation index, see [llms.txt](https://help.gleantap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.gleantap.com/settings/agency-and-partner-accounts.md).

# Agency & Partner Accounts

If you're a marketing agency, franchise operator, consultant, or reseller managing Gleantap for multiple businesses, an **agency account** (also called a **partner account**) gives you a single login that spans every customer account you manage.

This page covers how the model works and what an agency can do that a standard account can't.

***

## The account hierarchy

Gleantap's structure has four levels:

```
Agency / Partner Account
   └─ Customer Accounts (multiple, one per business)
        └─ Workrooms (multiple, one or more per account)
             └─ Locations (multiple, one or more per workroom)
```

**What each level is:**

| Level                | Description                                                                                               | Example                      |
| -------------------- | --------------------------------------------------------------------------------------------------------- | ---------------------------- |
| **Agency / Partner** | A parent account that oversees multiple customer accounts. Optional — only agencies and resellers use it. | "Growth Studio Partners LLC" |
| **Customer Account** | A single business's Gleantap presence. Owns billing, data, and users for that business.                   | "Sunrise Yoga Corporate"     |
| **Workroom**         | A workspace within a customer account. One or more per account. See Managing Multiple Locations.          | "Sunrise Yoga - East Coast"  |
| **Location**         | A physical club/studio. One or more per workroom.                                                         | "Sunrise Yoga - Boston"      |

A regular customer with a single business only sees the Workroom → Location layers. An agency spanning several customers sees everything from the top of the tree down.

***

## What an agency account can do

**Access every customer account from one login.** No password-swapping or duplicate logins. Switch between customers with a picker.

**See a unified dashboard.** Aggregated metrics across all customer accounts — total contacts, health status, monthly revenue, growth trends.

**Onboard new customers.** Create new customer accounts under the agency umbrella (usually coordinated with Customer Success — see [Getting set up as an agency](#getting-set-up-as-an-agency-partner) below).

**Apply consistent settings and branding.** Configure your own brand (name, colors, logo) that appears across the agency-level portal.

**White-label the experience.** Use your own domain and branded login so customer-facing pages look like your product, not Gleantap's.

**Manage billing your way.** Choose how each customer is billed — through you (with a revenue-share arrangement), directly to Gleantap, or a Stripe Connect model. Coordinate specifics with Customer Success.

***

## Getting set up as an agency / partner

Agency accounts are **created by Gleantap** — they aren't self-serve.

To get started:

1. Email <support@gleantap.com> or your Gleantap contact. Say you want to set up an agency/partner account.
2. You'll discuss:
   * How many customer accounts you expect to manage
   * Your business model (marketing agency, franchise network, consultant, reseller)
   * Billing preference (partner-card, Stripe Connect, or direct-to-Gleantap for each customer)
   * White-label needs (custom domain, branded login)
   * Revenue-share arrangement (if applicable)
3. We provision your agency account and configure the initial customer accounts.
4. You get a login for the agency dashboard, from which you can switch into any customer account.

Typical setup takes a few business days depending on complexity.

***

## The agency dashboard

Once your agency account is set up, logging in takes you to the **Agency Dashboard**. It shows:

* **All customer accounts you manage** — list view with search, filter, and status indicators
* **Aggregated metrics** — total contacts, monthly recurring revenue (MRR), account count by health status, growth over the last 6 months
* **Per-account details** — notes, current plan, assigned account manager, last contact, active/inactive status

Clicking a customer account name takes you into that customer's workspace as if you'd logged in directly. Switch back to the agency dashboard at any time.

***

## Adding new customer accounts under your agency

Two paths:

**A) Coordinated with Gleantap** — for larger onboardings or accounts with custom plan requirements, email your Gleantap contact. We'll provision the new customer account under your agency and connect it to your dashboard.

**B) Self-serve creation** — if your agency has been set up with self-serve account creation enabled, use the **Create Account** flow in the agency dashboard. You'll fill in the customer's name, contact info, timezone, country, and initial locations. The new account is created under your agency with a starter plan (typically a free trial that converts to paid).

Whether self-serve is enabled and what plans you can offer depends on your agency setup. Check with Customer Success if you're not sure.

***

## Billing models

Agencies pick a billing model per customer account. Three options are supported:

**Partner Card** — you (the agency) pay Gleantap. You then bill the customer separately at whatever rate you charge. A revenue-share arrangement determines what portion of the plan cost you pay vs keep as margin.

**Stripe Connect** — the customer pays a Stripe account you control. Gleantap takes an application fee off the top. Customers see the charge come from your business, not Gleantap.

**Direct Client** — the customer pays Gleantap directly. Simplest model; you don't handle the money.

The right choice depends on your business model, tax treatment, and how much you want to insert yourself into the payment flow. Discuss with Customer Success during setup.

***

## White-label

Agencies can white-label the customer-facing experience:

**Custom domain** — customers access their workroom at your domain (e.g., `app.yourbrand.com`) instead of `app2new.gleantap.com`. Uses standard CNAME/A record DNS setup; we help you configure.

**Branded login** — the login page shows your brand name, logo, favicon, and color scheme. Customers don't see Gleantap branding during login or in the main navigation.

**Branded emails and communications** — outbound emails to customers can be sent from your branded domain and email address.

To enable white-label, tell Customer Success what you want branded and provide:

* Your logo (light and dark versions)
* Favicon
* Brand color (hex code)
* Support email address for your customers
* The custom domain you want to use

Turn white-label on and off via a toggle in the agency-level branding settings.

***

## Common scenarios

### "I have five customer businesses — do I need five separate Gleantap logins?"

No. Set up an agency account. One login gives you access to all five (and any more you add later) with an account switcher.

### "Can my customer see other customers' data?"

No. Each customer account is completely isolated. Customers see only their own account when they log in. Only your agency-level admins see across accounts.

### "Can I create a new customer myself, or does it require support?"

Depends on your agency setup. If self-serve account creation is enabled for your agency, you can create new customer accounts directly from your dashboard. If not (or for accounts needing custom plans), coordinate with Customer Success.

### "One of my customers wants to leave. What happens?"

The customer account stays intact — you can either transfer it to their direct ownership (removing it from your agency), or archive it. Coordinate the transition with Customer Success so billing and permissions are handled cleanly.

### "How do I set different plans for different customers?"

The agency dashboard lets you assign different plans to each customer account, with per-account pricing. Plan floor prices apply (below which agency pricing isn't viable). Setup and pricing details are configured with Customer Success.

### "Can I see reports across all my customer accounts?"

The agency dashboard shows aggregated metrics — total contacts, MRR, health, growth. For campaign-level or message-level reporting, open each customer account individually.

### "Can I brand emails sent to customers?"

Yes — as part of white-label, outbound emails can go from your branded domain. Coordinate with Customer Success to configure sender authentication (DKIM, SPF) for your domain.

***

## Related pages

* Managing Multiple Locations — how workrooms and locations work within a single customer account
* Add / Remove Sub Users — teammate access within an account
* Billing — the standard customer billing model (contrast with the agency model above)
* Integrations — CRM syncs at the workroom level


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.gleantap.com/settings/agency-and-partner-accounts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
