# Browsing accounts

> Source: https://docs.trailspark.ai/accounts-dashboard/browsing-accounts

## The Companies area

**Companies** (the nav link in the left sidebar) is where you browse, search, and manage every account Trailspark is tracking. It lives at `/settings/org-management` and has three tabs:

- **Organizations** — the full account list with search
- **Review** — accounts waiting on a decision from you. The tab carries a count badge when something is waiting
- **Buying Groups** — the buying-group roster, grouped by ICP

## Organizations tab

The Organizations tab lists every account in your workspace as a table. Each row shows the account name and domain, signal count, lead count, link count, when the account was first seen, and three more columns described below: **Account fit**, **Outside activity**, and **Domain**.

Clicking a row opens the [account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail) page for that account.

### Account fit and Outside activity columns

Propensity tells you whether an account is *doing* anything in your product. Two more columns answer a different question: does this account *look like* your ideal customer, and is anything happening at that company outside your product?

- **Account fit** — how well the account's company profile (industry, size, region, market segment, and similar firmographic details) matches your ICP's own description. One of **Strong**, **Partial**, **Weak**, or **Unknown**. **Unknown** means Trailspark doesn't have enough company detail to judge fit yet — hover the badge for *"We don't have company details for this account yet."* — not that the account is a poor match.
- **Outside activity** — how recently something happened at the account outside your product: a funding round, a hiring push, a new partnership, and so on. One of **Hot** (within 7 days), **Warm** (within 30 days), **Cold** (within 90 days), or **None**, along with the most recent event.

**Neither column ever changes an account's propensity score.** They're a second and third read on the account, next to propensity, not an input to it.

Use the **Account fit** and **Outside activity** filters above the table to narrow the list the same way the other Advanced search filters work. There's also a **Fit but quiet** chip: it shows accounts with a **Strong** or **Partial** fit but a **Low** propensity, ordered by how recent their outside activity is. This is the list of accounts that look like your ideal customer but haven't shown up in your own product data — exactly the accounts a rep would otherwise scroll right past, because a low-propensity account and a hobby signup look identical without this second dimension.

Accounts that have never been evaluated can still receive an Account fit reading from their company profile.

### Domain column

The **Domain** column says what an account is named by, and what that means for your plan:

- **Company domain** — the account is named by a company's own domain. The ordinary case.
- **Personal email** — the account is named by a personal email address (a free webmail domain). *Personal email — not counted toward your plan.*
- **Excluded domain** — the account is named by a domain on your excluded-domains list. *Named by an excluded domain — counts toward your plan.* This is the one worth a look: you told us not to treat that domain as a company identity, but the account itself is still a real account and still counts. Open the account to see the state in full, with a link to **Manage excluded domains**.
- **No domain yet** — we haven't seen a company email address on this account. *No domain yet — not counted until a company email appears.*

Use the **Domain** filter above the table to narrow to any of the four. Like the other filters here, it applies across the whole list, not just the page you're looking at, and it combines with your search and Advanced filters.

Excluded domains are set per workspace in **Settings → General**, in the **Excluded domains** section. Changing that list changes how accounts read here.

### Search

A search box at the top of the tab filters the table as you type. It matches on more than just the name: the account name and domain, the ID or name of any product workspace linked to the account, plus firmographic details (industry, region, market segment, employee count) and any custom fields carried on the account. The search is debounced — results update shortly after you stop typing, and the table resets to page 1 on each new search.

### Advanced search

Click **Advanced** next to the search box to open a filter panel and narrow the list by specific attributes. Each filter is a row of **attribute → condition → value** — for example *Industry is Fintech*, *Employee count greater than 500*, or *Propensity is High*. Add as many rows as you need; they combine with AND (an account must match every filter). Available attributes include the company name and domain, Industry, Region, Market segment, Employee count, Propensity (High / Medium / Low / Not evaluated), Account fit (Strong / Partial / Weak / Unknown), Outside activity (Hot / Warm / Cold / None), buying-group stage, and a set of deal attributes drawn from your synced CRM deals: **Deal data** (Complete / Unknown), **Has an open deal**, **Open deals**, **Open deal value**, **Open deal type**, **Most recent deal outcome**, **Won business before**, **Deals won**, and **Deals lost**.

**Has an open deal is No** and **Won business before is No** only match accounts whose deal data is **Complete** — an account Trailspark hasn't finished reading yet is never swept into a "no" filter by mistake. **Open deal value** only appears once your workspace has a reporting currency set, or your open deals are all in one currency — see [Syncing deals](https://docs.trailspark.ai/crm-integration/connecting-hubspot#syncing-deals). See [Account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail#opportunities) for what these facts mean on one account.

#### Filtering on several values at once

One row can name **several values**, so you don't need a separate row for each — and because rows combine with AND, a separate row per value would match nothing anyway.

- **Fields you pick from a menu** (Industry, Market segment, Propensity, ICP, buying-group stage, Trial status) — open the value menu and tick every option you want. The button shows what you picked, with a count beside it.
- **Fields you type into** (Company name, Domain, Region, Plan) — type a value and press **Enter** to turn it into a chip, then type the next. You can also paste a comma-separated list — *Acme, Globex, Initech* — and each becomes its own chip. Click a chip's **×** to drop just that one.

With **is** or **contains**, an account matches if **any** of the values fit — a note under the box reads *Matches any of these*. With **is not**, it flips: the account has to match **none** of them, and the note reads *Matches none of these*. This is the same way values work in your [ICP rules](https://docs.trailspark.ai/icp-creation/icp-eligibility-qualification).

Firmographic filters such as Industry use the account's **best available** value — the value shown on the account, whether it came from your CRM or from data enrichment — so filtering by *Industry is Fintech* also finds accounts whose industry was filled in by enrichment.

The attribute list also includes **your own fields**, tagged so you can tell them apart: your CRM custom account fields (**(Custom)**), product-org details like plan name and trial status (**(Product)**), and any data-enrichment fields you've activated (**(Enrichment)**). So you can filter on things specific to your workspace — for example *Renewal Tier (Custom) is Gold*, *Plan name (Product) is Enterprise*, or *Funding Stage (Enrichment) is Series B*. The exact fields you see depend on what your CRM, product data, and enrichment provide.

Active filters appear as chips above the table; click a chip's **×** to remove it, or **Clear all** to reset. Your search and filters are reflected in the page URL, so you can copy the link to share the exact view, or save it as a reusable search (see [Searching across everything](https://docs.trailspark.ai/accounts-dashboard/search)).

### Domain groups

When two or more entries share the same domain, they are grouped under a single domain header row instead of appearing as separate rows. The header shows the domain name, total signal count, and total lead count across all entries in the group.

- **Pending unification** (amber badge) — the system queued these entries for automatic consolidation. No action required. Expand the row to see the individual entries; clicking any entry still opens its account detail page.
- **Conflict · N remaining** (red badge) — multiple CRM accounts claim the same domain and the system cannot consolidate automatically. See [Domain conflicts](#domain-conflicts) below.

### Domain conflicts

A domain conflict means Trailspark found more than one CRM account record connected to the same domain and needs you to decide how to route the entries that don't already belong to one of them.

Expand the conflict row to open an inline resolution panel. For each unassigned entry, pick which CRM account it should roll up to, or leave it unassigned for manual review later. You can also set a default CRM account for new entries that arrive under this domain going forward.

When you're done, click **Apply assignments**. Partially resolved conflicts stay visible until all entries are assigned.

## Buying Groups tab

The **Buying Groups** tab shows the buying-group roster: all accounts tracked under buying-group ICPs, grouped by ICP. Each group has a rollup summary, and each account row shows its current coverage status.

This roster is documented in full — including status labels, rollup counts, the renewal view, and the Between motions section — in [Account coverage](https://docs.trailspark.ai/buying-groups/account-coverage). The Organizations tab is the right place to search and navigate to individual accounts; the Buying Groups tab is where you read coverage at a glance across your whole account base.

To filter the roster to a single ICP, use the **ICP** dropdown at the top of the tab.

## Review tab — accounts waiting on a decision

The **Review** tab (previously called *Org Mapping*) is where Trailspark puts every account it could not sort out on its own. It flags them here instead of guessing, because guessing wrong in either direction is expensive: merge two companies that aren't the same and you get one scrambled account; leave one company split in two and you score half a buying group.

The tab carries a count badge, and the same number appears on **Companies** in the left sidebar and in the notification bell, so you can see there's work waiting without opening the tab.

**Nothing changes while an item waits.** Until you decide, the account keeps the name and domain it has today. Deciding is what changes it.

The tab has three views, chosen with the buttons at the top:

- **Needs attention** — the queue of decisions waiting for you
- **All accounts with multiple workspaces** — the full audit list of accounts that have more than one product workspace or more than one domain, whether or not anything is flagged
- **Domains** — every business domain your people carry, and every account it touches

### Needs attention — the queue

Items are grouped by account: one card per account, listing every decision that account owes. Use the **Pending** / **Resolved** buttons above the list to switch between what's waiting and what's already been decided. When nothing is waiting, the view reads **All caught up**.

Only **Owner** and **Admin** roles see the decision buttons. Everyone else can read the queue.

Five kinds of item can appear:

**A domain linked to more than one account** — for example *acme.com appears on 3 accounts*. The accounts are named and clickable underneath, each showing how many people are on it, so you can weigh every side before deciding. Your options:

- **Combine these accounts…** — opens a panel where you choose, for each account, which of the others it should become part of, then **Apply assignments**. You can also set a default so accounts that turn up on this domain later go the same way without asking again
- **Keep separate, related** — they're different companies but one owns the other; you pick the parent and the child, and Trailspark records the relationship
- **Keep separate, unrelated** — they're genuinely different companies with no connection

**Is this account's domain still right?** — for example *Is acme.com still the right domain for this account?* This one card gathers every open domain question for the account, however many there are. It shows who is actually on the account right now ("People currently on this account's workspace: 5 from bigagency.com, 2 from acme.com…"), notes when the person who originally carried the account's domain is no longer there, and tells you where newcomers from other domains have been filed instead. Trailspark has already erred on the side of caution — nobody was folded in without asking. You pick exactly one answer:

- **Keep acme.com** — the current domain is right; this resolves every open question on the card at once
- **Switch to bigagency.com** — one row per candidate domain, each showing its evidence ("5 people across 2 workspaces"); picking one makes it the account's domain and re-scores the account
- **Exclude** — a small side-action on each candidate row: that domain is an agency, consultancy, or contractor and should never stand for a company again anywhere in your workspace (see [Excluded domains](https://docs.trailspark.ai/team-management/site-settings#excluded-domains))

**This account's people span two company domains** — for example *This account's people span acme.example (4) and acme-labs.example (2). Keep acme.example, or use acme-labs.example?* This card appears when the people already on one account — or the company record your CRM linked to it — come from more than one company domain, and Trailspark can't tell on its own which one should name the account. Nothing was changed and **scoring does not pause while this waits**: the account keeps its current domain and keeps being scored until you decide. Sometimes one of the domains comes from the account's CRM record rather than from a person; the card says so. You pick one answer:

- **Keep {current domain}** — the account keeps its name. Trailspark remembers that you looked at these domains together and won't ask about the same pair again; it only asks again if a genuinely new domain turns up on the account later
- **Switch to {other domain}** — that domain becomes the account's name (the old one is kept as a secondary domain) and the account is re-scored. This is the one place a domain on your [Excluded domains](https://docs.trailspark.ai/team-management/site-settings#excluded-domains) list can be chosen as an account's name — an agency-named account is a real account, and you've said so
- **Exclude** — the same side-action as above: that domain should never stand for a company anywhere in your workspace

If the domain you switch to already names another account, Trailspark won't create a second account with the same domain. Instead it adds a *"domain linked to more than one account"* item to the queue and opens it for you, so you can decide whether the two are one company.

**Which workspace should scoring lean on?** — for example *This account has 3 workspaces. Scoring currently considers all of them.* Nothing is wrong here — scoring already works across every workspace. Each workspace appears as a row with its own evidence (people, product activity, users, and revenue where tracked), with the one Trailspark would pick tagged **Suggested** and the reason beside it. Choose **Base scoring on this workspace** to make one workspace the anchor (the account re-scores), or **Use all workspaces** to keep scoring across the whole account and stop being asked. See [account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail) for what "Scored workspace" means.

### Keep separate is remembered

When you choose any flavour of **Keep separate**, that decision sticks. Trailspark will not raise the same question again, however many new signals arrive for those accounts. This is the main thing the Review tab does that a plain notification list doesn't. The same is true of both answers on a *"people span two company domains"* card: keep or switch, the pair you decided on is not raised again — only a new domain reopens the question.

### Which items pause scoring

Most items in the queue **pause scoring** for the accounts they name until you decide, because scoring an account under the wrong identity is worse than waiting: a domain linked to more than one account, linked accounts, and the *"is this account's domain still right?"* question raised when someone from a different company signs into an account's own product workspace all hold. The *"people span two company domains"* card is the exception — the account is already named and keeps being scored while it waits.

If a situation genuinely goes away on its own — the person leaves, the domain disappears from the workspace — the item closes itself and appears under **Resolved** labelled **Closed automatically**, with the specific reason spelled out (for example *the conflicting domain is no longer present in this workspace*, or *one outsider among many, kept separate*). Items you decided read **Kept separate by you**, **Resolved**, or **Merged**.

### Reopening a decision

Switch to **Resolved** and click **Reopen** on any item. It returns to **Pending** unchanged, and the decision stops being remembered. Useful when you keep something separate and then learn otherwise.

### Switching an account's domain

**Switch to {domain}** is the one action that renames an account. The old domain isn't thrown away — it's kept on the account as a secondary domain, so anyone who arrives on it still lands in the right place. The account is re-scored shortly afterwards, because its identity changed. When the card carried several open questions, switching answers all of them: the domain you picked wins, and the others are recorded as kept separate.

You can only pick a domain the account's own people actually use, or one the flagged item named. Personal email domains (Gmail, Outlook, and similar) are always refused. A domain on your [Excluded domains](https://docs.trailspark.ai/team-management/site-settings#excluded-domains) list is refused too, with one exception: when a *"people span two company domains"* card lists it, you can choose it from that card.

### All accounts with multiple workspaces — the audit list

The second view is the full picture rather than just the flagged part. One row per account with more than one workspace or more than one domain:

| Column | What it shows |
| - | - |
| **Account** | the account name, linked to its detail page |
| **Domains** | the account's main domain, with any secondary domains underneath. An amber dot marks accounts that have something pending |
| **Workspaces** | how many product workspaces are linked |
| **Scored workspace** | which workspace scoring runs against, and why it was picked. When none has been chosen, the cell shows **None yet · See suggestion** |
| **Pending** | how many decisions this account owes |

Use this view to audit your account base — for example, to check that every multi-workspace account is being scored against the workspace you'd expect — rather than to work through a queue.

### Domains — where a domain shows up across your accounts

The third view lists every business domain your people carry, and every account it touches. It's how you spot an agency, consultancy, or shared vendor domain before it links accounts together that shouldn't be — the same pattern an [excluded domain](https://docs.trailspark.ai/team-management/site-settings#excluded-domains) is meant to catch.

| Column | What it shows |
| - | - |
| **Domain** | the domain itself. Carries an **Excluded** badge if it's already on your [Excluded domains](https://docs.trailspark.ai/team-management/site-settings#excluded-domains) list |
| **Accounts** | how many accounts this domain touches |
| **Linked** | accounts where this domain is confirmed as belonging to the account |
| **People only** | accounts where people use this domain, but it hasn't been confirmed as belonging to the account |
| **Declined** | accounts where this domain was already said *not* to belong |
| **People** | how many people across all those accounts carry this domain |

Domains that touch the most accounts sort to the top — a domain on many accounts is either a shared employer worth knowing about, or a sign that some of those accounts should be looked at together.

Click a domain to expand it and see the individual accounts: each shows its name, how many workspaces it has, how many of this domain's people are on it, and whether the domain is Linked, People only, or Declined there. An account that has since been merged into another shows as "now part of {account}" instead of its own row. A domain that touches a lot of accounts shows only the busiest ones, with a note telling you how many more there are.

**Owners and Admins** see an **Exclude domain…** action on each row. Excluding a domain stops it from linking accounts together or standing in for a company going forward; accounts it already links stay exactly as they are. Everyone else can read the list.

### The daily email

Once a day, Trailspark emails your workspace's Owners and Admins a summary of what's waiting: how many accounts need a look and what kind of decision each one needs. It arrives in the morning (Pacific).

You get it **at most once a day, and only when something is actually waiting** — an empty queue is never emailed. Inside the same day, a second email goes out only if the number waiting has grown. If you're working through the queue and the number is going down, Trailspark stays quiet.

## Opening an account

From any tab, clicking an account name or row navigates to the [account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail) page, where you'll find coverage, roles, the signal timeline, and the full buying-group picture for that account.

## Next steps

- [Account detail](https://docs.trailspark.ai/accounts-dashboard/account-detail) — coverage, roles, timeline, and the full buying-group picture for one account
- [Account coverage](https://docs.trailspark.ai/buying-groups/account-coverage) — how coverage stages and role states work, and the full buying-groups roster reference
- [Browsing leads](https://docs.trailspark.ai/accounts-dashboard/browsing-leads) — the full leads list, filterable by score and account
- [Lead detail](https://docs.trailspark.ai/accounts-dashboard/lead-detail) — activity history and score breakdown for one person
- [Site settings](https://docs.trailspark.ai/team-management/site-settings#excluded-domains) — the Excluded domains list that stops agency and consultancy domains from standing for a company
- [Buying groups overview](https://docs.trailspark.ai/buying-groups/buying-groups-overview) — how buying groups are built and tracked
- [ICP overview](https://docs.trailspark.ai/icp-creation/icp-overview) — setting up ICPs and role definitions