Does an invited teammate get their own separate account?

No. They get their own login (their own email and password/OAuth, or your single sign-on), but it operates inside YOUR account: same attribution data, same budgets, same providers. What they can see and change is decided by the role you give them.

What roles are there?

Owner (the account creator), then Admin, Developer, Finance and Viewer for teammates. New invites default to Viewer, the least privilege. See Roles & Permissions for exactly what each can do.

Who can change roles?

Owners and Admins can invite people and change roles, but only the Owner can grant or remove the Admin role. That stops an admin from promoting themselves or a friend.

How many teammates can I invite?

Depends on your plan: 1 seat (solo, no invites) on Free, 3 on Base, 10 on Growth, 25 on Business. A pending (not-yet-accepted) invite still counts against your seat limit.

What happens if I revoke a teammate's access, or change their role?

Both take effect within seconds. A revoked teammate loses access on their very next request, and a role change is applied on their next request too. No separate logout step is needed.

Can someone who already has their own Cognocient AI account be invited to mine?

No. If the email already has its own Cognocient AI account, the invite is rejected with a clear error rather than merging two accounts. Invite a teammate who is new to Cognocient AI, or have them use a different email.

How do I invite teammates into my Cognocient AI account?

Invite teammates into your existing Cognocient AI account with a role: one shared account, seat limits by plan, and how access is controlled.

Invite teammates into your existing Cognocient AI account from Settings → Team. They sign up (or log in) with their own email, but land inside your account: same real-time attribution, same budgets, same connected providers. There's no separate "their data" vs. "your data". It's one shared account with more logins, and each login has a role that decides what it can change.

Not a separate account, not a new tenant

An invited teammate's login is mapped onto your account rather than creating a new one. This means: no data migration if someone leaves and comes back, no duplicate provider connections to manage, and a revoked teammate loses access on their next request, with nothing to clean up.

Seat limits by plan

Plan	Seats
Free	1 (solo, no invites)
Base	3
Growth	10
Business	25

A pending invite (sent but not yet accepted) still counts against your seat limit, so you can't over-invite past your cap while several invites sit unopened.

If your plan shrinks

Seat limits are also enforced when a plan gets smaller. If you downgrade below your current headcount (for example to Free, which is solo), the newest members beyond the new limit are suspended automatically, once a day. A suspended member keeps their role and history but loses access, and cannot get back in through SSO or SCIM. When you upgrade, suspended members are reinstated, oldest first, up to the new limit. Each suspension and reinstatement is written to the audit log. The account owner is never counted or affected.

On the Business plan you can also provision members automatically with SCIM.

Inviting someone

Go to Settings → Team.
Enter their email, choose a role, and click Send invite.
They receive an email with a one-time link. Opening it walks them through signup and drops them straight into your dashboard, with no separate onboarding wizard. (If that email already has its own existing Cognocient AI account, the invite fails with a clear error instead.)

The role defaults to Viewer so nobody gets more access than you meant to give. Change it any time from the same page.

Roles

Role	In one line
Owner	The account creator. Everything, including billing.
Admin	Everything except billing: team, SSO, provider keys, budgets, routing.
Developer	Proxy keys, routing rules, Auto Router, emergency freeze, ingest and exports.
Finance	Budgets, chargeback, shadow spend, reports and exports.
Viewer	Read-only dashboards and reports.

The full permission matrix is in Roles & Permissions.

Only the Owner manages admins

Granting the Admin role, demoting an Admin, or removing an Admin is reserved for the Owner. Admins can manage everyone else.

Changing a role

From Settings → Team, use the role menu next to a teammate. The change is recorded in the audit log with the old and new role.

Removing a teammate

From Settings → Team, click the remove icon next to their name. Access is revoked immediately, with no grace period and no way for a removed member to keep working with cached credentials, since every request re-checks their access on the backend.