Does Jarvis support team accounts?

Yes, on Pro and Unlimited tiers. Team accounts let you invite teammates under a shared billing account, with shared memory (optional), shared connector configurations (optional), and per-seat usage tracking. Open Settings → Team to invite members by email. Each member gets their own Jarvis (getjarvis.eu) app sign-in but billing rolls up to the account owner. Pro is $16/user/month; Unlimited is $32/user/month, with volume discounts above 10 seats. Shared memory is opt-in per memory entry — useful for team knowledge (project nicknames, shared contacts) but disabled by default to protect individual privacy. Each member's connectors (Gmail, Slack, etc.) are personal by default; admins can configure shared workspace-level connectors. GDPR-aligned for GDPR compliance. Works on macOS, Windows, and Linux. Free tier is single-user only.

Three components. (1) Billing: the account owner pays for all seats. Stripe handles billing, with EU VAT calculated automatically for European customers. Per-seat pricing means each team member adds $16 (Pro) or $32 (Unlimited) to the monthly bill. Annual billing offers a discount. (2) Membership: invite members by email from Settings → Team. They receive a sign-up link, create their Jarvis account, and are bound to your team's billing. Members can be Admins (manage team, billing, settings) or Members (use Jarvis with their own account). (3) Workspace: a team has shared resources optionally — shared memory entries, shared Quick Prompts, shared connector configurations (e.g., the Slack workspace OAuth grant can be team-wide). Workspace defaults to nothing shared; the admin opts in per resource.

Memory is personal by default — your tone profile, your priority contacts, your project notes — and stays on your personal account even within a team. Two opt-in paths for sharing. (1) Per-entry sharing: when Jarvis writes a memory entry, you can mark it shared with the team. Useful for team-level knowledge: "Project Atlas" is our Q4 product launch, the engineering team uses #eng-bugs for triage. (2) Team workspace memory: admins can create memory entries that apply to all members (e.g., the company's brand voice for drafting). Members can opt out of inheriting workspace memory if they prefer pure personal context. Shared memory is encrypted AES-256-GCM like personal memory, GDPR-aligned on GDPR-aligned infrastructure. Only team members can read shared entries; the encryption boundary is per-team, not per-user, for shared content.

Pricing