> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/pipeline/accounts.md).

# Accounts

The [Accounts page](https://app.spara.co/accounts) shows the companies in your pipeline, synced from your CRM. Each account groups the leads at that company alongside its firmographics and the owner responsible for it, so you can understand engagement at the company level — not just lead by lead.

<figure><img src="/files/nEUgHrCa1QuFqZCyHolS" alt=""><figcaption><p>The Accounts page, showing companies synced from your CRM with their industry, size, and owner.</p></figcaption></figure>

## Account details

Click any account to open its detail view — a single card summarizing everything Spara knows about the company. The detail view includes:

* **Firmographics** — Website, Industry, Employees, Annual Revenue, and Billing City.
* **Owner** — The person responsible for the account. Click through to their [Owners](/pipeline/owners.md) record.
* **Leads** — How many leads Spara has engaged at this company. Click the count to open those leads on the [Leads page](https://app.spara.co/leads).
* **CRM Source** — Which CRM the account synced from. Click **View in HubSpot** or **View in Salesforce** to open the record in your CRM.
* **Custom fields** — Any account-level [Data Model](/build/data-model.md) fields your team has configured appear at the bottom of the card.

## Syncing from your CRM

Accounts are synced from your connected CRM — Salesforce, HubSpot, or Marketo — when account syncing is enabled. Spara keeps them up to date as records change in your CRM, so the Accounts page reflects your source of truth without manual entry.

If your Accounts page is empty, either no CRM is connected or account syncing is turned off. See [CRM Integrations](/integrations/crm-integrations.md) to connect a CRM, and reach out to your Spara customer success representative to enable account syncing.

{% hint style="info" %}
For a full picture of how Spara's data model operates and syncs with your CRM, see [https://docs.spara.com/developers/data-model](https://docs.spara.com/developers/data-model "mention").
{% endhint %}

## FAQ

### Why is my Accounts page empty?

Accounts only populate from a connected CRM with account syncing enabled. Connect Salesforce, HubSpot, or Marketo under [**Settings > Integrations**](https://app.spara.co/organization/integrations), then confirm account syncing is on. If a CRM is already connected, contact your Spara customer success representative to turn on account syncing.

### How are accounts linked to leads?

Spara matches each lead to a company account so you can see all engagement at that company in one place. The account detail view shows the number of related leads, and you can filter the [Leads page](https://app.spara.co/leads) by account.

### What does the Owner column show?

The owner is the person in your CRM responsible for the account — typically the assigned sales rep or account owner. Owners are managed on the [Owners](/pipeline/owners.md) page.

### Can I add custom fields to an account?

Yes. Account-level fields defined in your [Data Model](/build/data-model.md) appear in the account detail view alongside the built-in firmographics.


---

# 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://docs.spara.com/pipeline/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.