Skip to content

Organisations (company grouping) ​

Every company can carry an optional Organisation label — a free-text grouping field used to slice the dashboard signal feed by parent organisation, region, division, or any other label that matters to your team.

What it is ​

  • A nullable text field on each company. Not required.
  • One organisation per company (not multi-tag).
  • Trimmed at the API edge — " Acme " and "Acme" collapse into the same bucket.
  • Distinct from the tenant scope. The tenant scope is your email domain; the organisation field is a user-defined label that lives inside your tenant.

Where you set it ​

SurfaceHow
Add company dialogOptional input below the Owner field — "Organisation (optional)"
Company pageInline editable field alongside Owner, Industry, etc
Company detail dialogShown in the meta grid; edit via the Company page
Import wizardMap a column to "Organisation" — auto-detects headers organisation, organization, parent organisation, group, division, territory
Imported data modalPer-row inline editor — set or clear for any row

Saving an empty value clears the field (NULL) instead of storing an empty string.

Where it filters signals ​

Once at least one company has an organisation set, an Organisation dropdown appears in the dashboard filter bar — between Source and Date. It mirrors the Source control:

  • Multi-select checkboxes inside a popover
  • Selecting multiple labels OR-matches signals from companies in any of them
  • "All" (zero selected) = no organisation filter
  • The dropdown auto-hides if no company has an organisation yet

The selection threads through the same backend route that powers the rest of the feed. We resolve the labels to a company-id IN list server-side so the filter composes cleanly with search + date + source + signal-type filters.

The chip on each signal row ​

When the Organisation filter has at least one label selected, signals whose company belongs to a selected org get a small chip next to the source tag. Acts as a "why this row is in your filtered view" affordance — selecting two orgs and seeing the chip makes it obvious which bucket each row came from. Truncates at ~10 chars with a tooltip on hover for the full label.

Clear the filter (zero selected) and the chip hides for every row to keep the feed visually quiet.

Bulk-setting via re-import ​

Update the organisation column in your source spreadsheet and re-import via Settings → Import companies. The import path:

  • Skips rows that already exist (matched by LinkedIn slug or company name)
  • Inserts only new rows

So re-importing does not overwrite the organisation on existing rows. To bulk-edit existing companies, use the Imported data modal — search/filter to scope, edit cells, hit Save row.

Why "Organisation" not "Org" ​

The codebase already has an org column on every table — it's the per-tenant scope key (your email domain). The organisation field is a separate user-facing concept layered on top. We kept the verbose name to keep the two readable side-by-side in code reviews and SQL.

Client Pulse — buying signals for your target accounts. Privacy · Terms · Open app ↗