Team members and roles

What this page is

Team & Access is where an admin invites colleagues into IQ, assigns them a role, and removes access when someone leaves. It is the single place the roster of who can work with IQ lives, alongside the one shared inbound address the whole team forwards documents to.

IQ never decides who belongs on your team. It surfaces the roster, the pending invites, and the plan's capacity, and the admin makes every call: who to invite, what role they get, and when to remove them.

Where to find it

Open Settings from the sidebar, then Team & Access at /settings/team. The page is admin-only: if you sign in with the User or Data contributor role, the page redirects you back to the main Settings screen. Only Admins (and the account's Owner, who is always an Admin) can reach this view.

The header: Operators Working with IQ

At the top of the page, the heading reads Operators Working with IQ, with a line underneath showing your capacity:

• "X of Y Operators", where X is how many Admins and Users are active on your account right now, and Y is your plan's cap.
• If you have any unexpired pending invites for an Admin or User role, it adds "· N pending".

Data contributors are never counted in this line. They forward documents and don't consume a spot on the plan, so inviting one never moves this number.

If your plan's capacity hasn't loaded yet, the line falls back to a plain member count instead ("N members").

The three roles

Every person on your team holds exactly one of three roles:

| Role | What it means | |---|---| | Owner | The account holder. Manages billing and the membership, invites and removes Operators, edits company settings, plus everything an Admin can do. There is exactly one Owner per account, shown as the billing contact. | | Admin (shown as "{Tier} Admin", e.g. Premier Admin, Executive Admin) | Full access at your plan's tier: acts on decisions, chats with IQ, uploads documents, exports data, and can manage the team. Counts toward your Operator cap. | | Data contributor | Forwards emails to IQ and uploads documents. No access to decisions, benchmarks, or IQ chat. Doesn't count toward the Operator cap, on any tier. |

A short reference card repeating these three descriptions sits at the bottom of the page under Role Descriptions, so you don't have to scroll back up to check what a role can do.

Inviting a teammate

1. 1Click Invite member, top right of the page.
2. 2Fill in their Name and Email.
3. 3Choose their Role: the tier-qualified Admin option (labeled for your plan, e.g. "Premier Admin") or Data contributor.
4. 4Click Send invite. IQ emails them a signup link and, once they accept, they appear in the table below.

Invite member is a Premier capability. On a Contributor or Executive account, the button itself is dimmed with a small "Multi-Operator access · Premier" tag, and clicking it opens an upgrade prompt instead of the invite form, even for a Data contributor invite that wouldn't count against your Operator cap. Premier and Reserve accounts get the working invite form directly.

If you're on Premier or Reserve and adding another Admin or User would push you past your plan's Operator cap, the form shows: "Your plan includes {cap} Operators working with IQ. You're at {current}. Remove an Operator or contact us to discuss expanding." and the Send invite button disables. Data contributor invites are never blocked by this, since they don't count against the cap.

Per-tier caps, for Admin and User roles only (Data contributors are always unlimited):

| Tier | Operator cap | |---|---| | Contributor | 1 | | Executive | 1 | | Premier | 5 | | Reserve | 15 |

The team table

Below the invite button, one row per active teammate:

• Name. Avatar, display name (or "Unnamed" if no name is on file), and a "(you)" tag next to your own row. The Owner's row carries a copper Billing contact badge, with a tooltip explaining "Stripe receipts and renewal notices go to this Operator." A job title, if one is on file, shows underneath the name.
• Email. The teammate's sign-in email, or a dash if none is on record.
• Forwarding address. The one email address your whole company forwards documents to (built from your account's inbound token). It's the same address in every row, not a personal one per teammate: attribution to who sent a document comes from the sender's own email, not a separate address per person. Click it to copy; the label flips to "✓ copied" for a couple of seconds. If no forwarding address exists yet, this shows a dash.
• Role. For your own row and the Owner's row, this is plain text (you can't change your own role, and the Owner's role isn't reassigned here). Every other row shows a dropdown you can change on the spot, no separate save step, it applies the moment you pick a new value and confirms with "Role updated."
• Joined. The date their access was created.
• Actions. A Remove link (not shown on your own row) and, for Admin-to-Admin changes only, a Set as billing contact link.

Removing a teammate

Click Remove on their row. A confirmation reads: "Remove {name} from the team? They will lose access to all company data." Confirming deletes their access immediately. A few guardrails:

• You can't remove your own row.
• You can't remove the billing contact. Reassign billing to someone else first (see below), then remove them.
• You can't remove the last remaining Admin. IQ blocks it with: "You can't remove the last admin. Promote another Operator to admin first."

Demoting an Admin to User or Data contributor carries the same last-Admin protection: "You can't demote the last admin. Promote another Operator to admin first."

Billing contact

Exactly one person per account is the billing contact, the Owner. Stripe receipts and renewal notices go to whichever email is on that row. To move it, click Set as billing contact next to another Admin's name (this link only appears on Admin rows, since only Admins are eligible). A confirmation reads: "Set {name} as the billing contact? Stripe receipts and renewal notices will go to them." Confirming moves the badge and the Stripe customer email to that person.

Pending invites

If anyone has been invited but hasn't accepted yet, a Pending Invites list appears below the team table. Each row shows the invited email, their role, when they were invited, and either an expiry date or an Expired flag (expired rows appear dimmed). Two actions per row:

• Resend, re-fires the invite email and extends the expiry by seven days. Useful if the original email was missed or the link expired.
• Cancel, revokes the invite before it's accepted. A confirmation reads: "Cancel the invite to {email}? They won't be able to accept it after." Cancelling immediately frees up any capacity that invite was holding.

An invite that expires without being accepted or canceled stops counting against your Operator cap on its own, you don't need to clean it up manually to free the spot, though the row stays visible (marked Expired) until you cancel or resend it.

Empty states

If your team table has no rows at all (a state you're unlikely to see in practice, since an admin viewing this page is themselves an active row), it reads: "No team members yet. Invite someone to get started." The Pending Invites list simply doesn't render at all when there are no open invites.

Best-practice example

Say you're on Premier with 3 of 5 Operators used. A new operations hire needs to act on decisions and chat with IQ day one, so you invite them as an Admin (it will show as "Premier Admin" once they accept). A separate accounting contractor only needs to forward AP invoices and W-9s, no benchmarks or decisions, so you invite them as a Data contributor instead: it doesn't touch your 5-Operator cap at all. Three months later the operations hire leaves. Before removing them, you check they aren't your billing contact; they aren't, so you click Remove, confirm, and their access ends immediately. Your capacity line drops back to "2 of 5 Operators."

Related reading

• The decision workspace, what an Admin or User role actually gets you access to once you're on the team.
• Acting on decisions, the day-to-day work an invited Admin or User does inside IQ.
• Forwarding documents, how the shared forwarding address on this page feeds your account, and what a Data contributor's forwarding-only access covers.
• Connecting your data, the other ways data flows into IQ beyond your team's inboxes.
• Benchmarks overview, the peer intelligence that Admin and User roles can see and Data contributors cannot.