Teams & Multi-User

​

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.

​

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.

​

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 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).

​

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 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, and it sends from the owner’s connected accounts. Anyone who can open the deal can turn it off.

​

Personal connections, shared results

Each teammate connects their own LinkedIn and Instagram from 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.

​

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.

​

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.

​

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