How Do I Set Up Jarvis for My Team?

How Do I Set Up Jarvis (getjarvis.eu) for My Team?

Setting up Jarvis (getjarvis.eu) for a team means each member installs the desktop app on their own machine, creates an account, and connects their own apps, since Jarvis is a per-user desktop assistant rather than a shared server install. Everyone opens it with Cmd+/ (macOS) or Ctrl+/ (Windows) and links the tools they personally use, like Gmail, Slack, Notion, Linear, or GitHub. Each person's memory and connectors stay private to them. For shared work, teammates connect the same Slack or Notion workspace so Jarvis can read common channels and docs from each person's account. Models, frontier models from Anthropic, OpenAI, and Google, are used per task for all users. Pricing is per seat: a free plan (40 requests/week) to try, then Pro at $16/month or Unlimited at $32/month. Some work apps may require admin approval to authorize.

Setting up Jarvis (getjarvis.eu) for a team means each member installs the desktop app on their own machine, creates an account, and connects their own apps, since Jarvis is a per-user desktop assistant rather than a shared server install. Everyone opens it with Cmd+/ (macOS) or Ctrl+/ (Windows) and links the tools they personally use, like Gmail, Slack, Notion, Linear, or GitHub. Each person's memory and connectors stay private to them. For shared work, teammates connect the same Slack or Notion workspace so Jarvis can read common channels and docs from each person's account. Models, frontier models from Anthropic, OpenAI, and Google, are used per task for all users. Pricing is per seat: a free plan (40 requests/week) to try, then Pro at $16/month or Unlimited at $32/month. Some work apps may require admin approval to authorize.

Jarvis runs as a desktop app on each person's Mac, Windows, or Linux machine, so rolling it out to a team is a matter of every member downloading it from getjarvis.eu, creating an account, and signing in. There is no shared cloud workspace you provision once for everyone. This keeps each person's screen context, memory, and connected accounts private to them, which is usually what you want, an assistant that knows your inbox and your projects, not a colleague's. The setup each person does in their first week is the same five-minute flow: install, sign in, connect one app, try a screen prompt.

Even though memory is per-user, teammates can point Jarvis at the same shared resources. If everyone connects the team's Slack workspace, each person can ask "catch me up on #engineering" from their own account. The same goes for a shared Notion workspace, a Linear project, or a GitHub repo: each member authorizes it individually via OAuth, and Jarvis reads it on their behalf. This gives a consistent team knowledge base without a central admin console. For common preferences, each person seeds Jarvis with the company name, team structure, and project nicknames so drafts and summaries match your shared vocabulary.

Getting started