Team members

Invite unlimited teammates to your company on any plan, and share one view of the truth.

Unlimited, on every plan

Recited never bills per seat. Every plan, including Launch, allows unlimited team members. This is deliberate: AI visibility work spans marketing, content, product, and leadership, and a per-seat price would mean most of those people looking at screenshots instead of data.

Inviting people

Members belong to the company, the top-level account that also holds billing and projects (see projects and companies). Invite teammates from Company settings under Members. An invited member gets access to the company's projects and everything in them.

What teammates see

Everyone works from the same live data:

  • The same dashboards, deltas, and answer log. When a number is questioned, anyone can open the chat behind it, which ends most debates quickly.
  • Shared project state: bookmarks on sources, prompt tags, and the status of opportunities (dismissed, drafting, published) are project-wide, so decisions made by one person are visible to all.
  • The in-app AI agent, which any member can use to ask questions in plain language. Agent usage draws from the project's shared daily allowance; see rate limits.

Working patterns that fit

A few divisions of labor that teams settle into:

  • A weekly owner for the reading routine: Since last scan movers, leaderboard deltas, and momentum. Ten minutes a day beats an hour on Fridays.
  • Content writers live in opportunities and the editor, working the scored backlog top down.
  • Whoever owns partnerships or PR works Missing citations, since earning mentions on cited sources is outreach, not writing.
  • Leadership gets the Overview page, where the stat strip and movers tell the story without requiring any digging.

Access notes

  • Anything published through the article API is controlled by API keys, not member accounts, so your site integration does not depend on any individual person.
  • API keys are created and managed per project by members; treat key management with the same care as any credential. See API keys.