> ## Documentation Index > Fetch the complete documentation index at: https://docs.every.ai/llms.txt > Use this file to discover all available pages before exploring further. # Teams & Multi-User > Invite teammates into one organization with shared records, per-member ownership and attribution, private agent chats, and per-user Google connections ## Overview An Every organization can have more than one member. Everyone in the org shares the same business records — people, companies, invoices, proposals, and pipeline deals — while a few things stay personal to each member: their agent chats can be kept private, and each person connects their own Google account. > [!NOTE] > > Multi-user behavior only appears once your org has **two or more members**. Solo organizations see the single-user experience with none of the team UI below (no avatars, no "Owner" labels, no All/My filters). ## How sharing works Every uses a simple two-layer model: * **Shared by default.** All business records — people, companies, invoices, proposals, and deals — are organization-wide. Every member sees every record. There is no per-record or role-based access control on business data. * **Personal where it matters.** Agent chat threads can be made private to a single member, and Gmail / Google Calendar / Google Contacts connections are scoped per person rather than per org. > [!NOTE] > > AI credits are a single **organization-wide pool** — all members draw from the same balance. There is no per-seat metering or per-member usage breakdown. ## Inviting teammates Open **Settings** at the bottom of the desktop left rail, go to **Business** (`/settings/organization`), and find the **Team** card. Click **Invite teammate** and add them by email — they'll receive an invitation link that adds them to this workspace once they sign in. The Team card also lists current members with their avatar, name, email, and role. You can also just ask the agent: *"invite [dana@example.com](mailto:dana@example.com) to this workspace."* It confirms the address with you before sending. ### Seats and plans Inviting teammates requires the **Team plan**. On a single-seat plan the Team card shows **Add teammates with Team** instead of the invite button, linking to **Settings → Billing** (`/settings/billing`). | Plan | Members included | | - | - | | Team | 5 | | Solo (and free/legacy plans) | 1 — the owner only | > [!NOTE] > > Seat limits are enforced when the invitation is created, so a workspace that has used all its seats can't invite anyone else until it upgrades. Existing teams that already exceed a limit are never reduced — nobody gets removed when plans change. > [!NOTE] > > Business records are shared across the workspace. Workspace administration is separate: admins manage invitations, business settings, billing changes, and finance connections. Teammates can view shared business and billing information without changing those settings. ## Ownership & attribution In a multi-member org, records show **who created or owns them** so the team can see at a glance who is responsible for what. * Records carry an owner / creator, surfaced as an **avatar and "Owner" or "Created by" label** on cards, detail dialogs, and activity timelines. * Attribution is about responsibility and behavior — it is **not** a visibility gate. Non-owners still see (and can edit) shared records. ### Pipeline deal ownership The [Every Agent](https://docs.every.ai/ai/every-agent.md) pipeline gives ownership a functional role: * Every deal has an **owner**. The Pipeline shows all deals by default, with a **"My deals" filter** to narrow to the ones you own. * The deal detail dialog includes an **owner switcher**. The current owner or a workspace admin can reassign an owned deal to another member. * **Outreach is owner-gated.** Only a deal's owner can send its outreach — the owner's connected Gmail is used to draft and scan replies. Non-owners can read and copy the drafted message, but the send action is reserved for the owner. This is enforced on the backend, not just hidden in the UI. * **Auto mode is owner-gated too.** Only the deal owner can turn on [Auto mode](https://docs.every.ai/prospecting/auto-mode.md), and it sends from the owner's connected accounts. Anyone who can open the deal can turn it off. > [!TIP] > > If you can't send a teammate's outreach, that's by design — ask the owner to send, or ask the owner or a workspace admin to reassign the deal to you. ### Personal connections, shared results Each teammate connects their own [LinkedIn and Instagram](https://docs.every.ai/integrations/linkedin-and-instagram.md) from [**Agent → Connections**](https://app.every.ai/agent/connections). A connection belongs to the person who made it: only they can sync or send from it. The people, messages, and deal activity it imports are shared with the workspace. Open the LinkedIn or Instagram row to see which teammates have connected under **Team members**. Gmail accounts are connected per person too. Each one has a **Workspace access** control for whether teammates can use it or it stays private to its owner. See [Google Workspace](https://docs.every.ai/integrations/google-workspace.md#connecting-more-than-one-gmail-account). ## Private agent chats Each agent chat thread has a visibility setting: * **Organization (default)** — visible to every member of the org. * **Private** — visible only to the member who owns the thread. You can toggle a thread between Organization and Private from the thread menu when you own it. Private threads (and their messages) are hidden from teammates everywhere they're read. > [!NOTE] > > Threads that touch **personal Google data** (your Gmail, Calendar, Drive, or Contacts) and threads created by **scheduled tasks** — like your [Daily Brief](https://docs.every.ai/scheduled-tasks/daily-brief.md) — are automatically made private and locked so they can't be re-shared. This keeps one member's inbox and calendar content from appearing in a teammate's view. ## Per-user Google connections Google connections are **per member, not per organization**. Each teammate connects their own Gmail, Google Calendar, and Google Contacts under **Agent → Connections**. * The agent uses **your** Google account for your work — reading your calendar, scanning your inbox for replies, sending on your behalf. * The Connections page shows your personal connection status alongside which teammates have connected their own accounts. * For pipeline outreach, the agent uses the **deal owner's** Gmail to send and to scan for replies. > **[Connect Google Workspace](https://docs.every.ai/integrations/google-workspace.md)** > > Connect your own Gmail, Calendar, and Contacts ## Member identity Across the app, members appear as avatars (their photo, or initials when no photo is set) with a tooltip showing name and email. You'll see them on: * Pipeline deal cards and the deal detail dialog ("Owner") * Person and company activity timelines ("Created by") * The Team section in Business settings * The thread list, next to private-thread indicators All of this identity UI only renders in multi-member orgs. ## Next Steps > **[Every Agent](https://docs.every.ai/ai/every-agent.md)** > > How the AI agent works with your team's data > **[Google Workspace](https://docs.every.ai/integrations/google-workspace.md)** > > Connect your personal Gmail and Calendar > [!NOTE] > > **Need help?** Contact support at [hello@every.ai](mailto:hello@every.ai) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.