Team, projects and organizations

LeadHunter is multi-tenant by design, with two levels:

An Organization groups several projects — for example Acme Agency with a Bike shops project and a Pet stores project.
A Project owns the data and is fully isolated: accounts, products, campaigns, conversations, research, custom fields, saved views, channels, webhooks, Client Pulse, expenses, usage and costs, funnel and stats. Nothing crosses between projects, not even between two projects of the same organization.

An internal team running its own outbound usually has one organization with one project. An agency running outbound for ten clients typically has one organization and ten projects. See Organization, project and product for what lives where.

The project switcher

The project switcher in the top bar selects the active project. It shows the organization name (small, uppercase) above the active project’s name. Open it and the projects you belong to are listed grouped under their organization. Every page you see — Today, accounts, campaigns, Insights, Runs — is filtered to the active project, and the choice persists across sessions.

The switcher’s footer has two links:

Organization overview — opens the organization overview page.
Manage projects — opens the Projects page.

Organization overview

Organization overview (the fourth tab of Insights, or the project switcher’s footer) shows one organization at a time: its name as the heading, and tabs to pick another organization when you belong to several. Below it:

an outreach funnel added up across that organization’s projects you belong to;
a Projects in <organization> grid — click a project to make it active and open its Today page;
a New project button.

Projects page

Projects (Settings → Projects, or Manage projects in the switcher) lists every project you belong to, grouped under organization headers. Each header has a New project in <organization> link. Each project card shows its Accounts and Users counts and its Slug, and has a Delete action (permanent — it removes the project and all its data). Only a project owner can delete it, and the dialog asks you to type the project’s exact name first. When the project was the last one in its organization, nobody outside that project belongs to the organization and you own the organization, the organization is deleted with it; an organization that still has other projects, members of its own, or another owner, stays.

Settings in the sidebar is one entry. It opens on Products, and every settings page shows the same menu to move between them: Products, Custom fields, Next step templates, Client Pulse, Webhooks, Team and Projects. All but Projects apply to the active project.

Creating a project

Use New Project on the Projects page, New project in <organization> under an organization header, or New project on the organization overview:

Organization — pick one of the organizations you own or administer, or New organization (named after the project) to start a new one.
Project Name — e.g. “Bike shops”. The Slug is generated from the name.
Description — optional.

You become the new project’s owner. The organization’s members are added to the new project too, each with the role they have in the organization — so a team that works across all of an organization’s projects doesn’t need re-inviting every time.

Each project has its own usage tracking (LLM tokens, Maps calls, searches, user-entered expenses); read the cost per project under Usage and costs.

Roles

Organization roles

Role	Sees the organization	Creates projects in it	Edits it
Member	✓	✗	✗
Admin	✓	✓	✓
Owner	✓	✓	✓

An organization can’t be deleted while it still has projects.

An organization always has someone who can manage it: when one is created automatically for a new project, the project’s owner becomes the organization’s owner.

Project roles

Access to a project’s data is granted per project, from that project’s Settings → Team page, with the roles owner, admin and member.

Role	Data read/write	Invite, change roles, remove others
Member	✓	✗
Admin	✓	✗
Owner	✓	✓

Everyone in the project sees and edits the same data — there’s no per-account or per-campaign permission. Roles control team management, not data access.

A guard prevents the last owner from being removed or demoted — the project would otherwise become un-administrable. Add a second owner before stepping back.

Who sees what

You see an organization if you’re a member of it or of any of its projects.
Inside it, you only see the projects you belong to.
So you can give someone access to just one project of an organization: add them to that project’s team, not to the organization.

Adding a teammate to a project

Open Settings → Team with the project active.

Invite by email. Enter the teammate’s email and a role. If they already have a LeadHunter account and have confirmed that email address, they’re added to the project immediately. Otherwise they receive an invitation email pointing at signup, and the project attaches automatically once they confirm that email address (the confirmation link LeadHunter emails at signup) — nothing else to click. Signing up with the address is not enough on its own: the invite waits for the confirmation, so nobody can claim a seat by registering someone else’s address.
Invitations expire after 14 days and can be revoked from the pending-invites list. Re-inviting the same email replaces the earlier pending invitation. Inviting someone who is already on the team answers ”… is already a member of this project.” Two invites of the same address sent at the same moment (from two tabs, or an integration retrying) no longer fail: a registered person is added once and the second answer is that same message, and an unregistered address ends up with a single pending invitation.
Roles and removal. Owners change roles and remove members from the same page; anyone can leave a project themselves. The last-owner guard applies everywhere, also when two owners change roles at the same moment.

Signing in and out

Sign in with your email and password. Your email address must be confirmed first (the link LeadHunter emails at signup); until then the sign-in page answers “Email address not verified. Check your inbox for the confirmation link.” Forgot it? Forgot password? on the sign-in page emails you a reset link.
After 10 failed attempts in a minute from one network, sign-in pauses for a minute (“Too many sign-in attempts.”).
Logout (in the account menu, top right) ends the session on the server — the token stops working on every device and script that used it — and clears what the app kept on that browser (the active project, recently opened items, unsent drafts, cached data).
When a session expires mid-work, LeadHunter sends you to sign in and brings you back to the page you were on.

Revoking access

Removing a teammate from a project:

Does not delete the user’s account or their access to any other project.
Does not delete any accounts, campaigns, or messages the project stores — those belong to the project, not the user.
Does revoke the user’s access to this project immediately. The project disappears from their switcher on their next page load.

Data isolation — what crosses, what doesn’t

Surface	Scope
Accounts, contacts, status history	Per project. Never crosses.
Campaigns, conversations, expenses	Per project.
Custom fields and their definitions	Per project.
Saved views	Per project (+ optionally private per-user — see below).
Channels, webhooks, Client Pulse	Per project.
Research records, usage and costs	Per project.
Dedupe stack	Per project. The same business can exist in two projects as two separate rows; LeadHunter doesn’t merge them.
Score reuse	Per (Product, Account). Since both live in one project, scores never cross.
Outreach funnel on the organization overview	Added up across the organization’s projects you belong to. Read-only; no data moves.

Per-user vs per-project

A few things live on the User, not the project — so they follow you across every project you belong to:

Communication language — the default language you write in. Read by the message-language fallback chain when no other override applies. (The app itself is in English; there’s no separate interface-language setting.)
Recent-entities list — the Recent section in the command palette. Tracks what you opened, not what others did.

Everything else — saved views, custom field definitions, accounts, campaigns, conversations — lives on the project.

Saved views: shared vs private

Saved views (the Saved views menu on the Accounts list) are an exception worth knowing about. Each view is either:

Shared — visible and usable by every member of the project. Use these for canonical lists everyone references.
Private — visible only to the user who created it. Useful for scratch views or experiments before sharing.

You can flip a view between private and shared at any time if you own it. The same name can exist once as a shared view and once as your own private view.

Common patterns

Pattern	Setup
Solo operator	One organization, one project, you as owner.
Internal team	One organization, one project, teammates as members. Add a second owner before going on holiday.
Several lines of business	One organization, one project per line of business (each with its own accounts and funnel). Different things sold to the same accounts are products in one project instead.
Agency	One project per client, grouped under your agency’s organization. Give a client’s own staff access to their project only, via that project’s team page.

Already using LeadHunter before organizations?

Every existing project was given its own organization with the same name and the same members. Nothing changes for you until you add a second project — then choose the existing organization in the Organization field to group them.

Common pitfalls

Forgetting which project is active. Every page is scoped to the switcher. If your campaigns list is empty when you expected dozens, glance at the top bar before assuming the data’s gone.
Expecting organization members to see every project automatically. They’re added to projects created after they joined the organization. For an existing project, invite them from its Settings → Team.
Creating a project for what is really a product. If the accounts overlap, a second project means duplicate account rows that never merge. Use a second product instead.
Sharing private saved views by accident. Flipping shared → private hides the view from everyone except you.
Trying to remove the last owner. It’s refused. Add a second owner first, then demote or remove.