PlugsightDocs

Onboard a teammate

Plugsight has no shared team accounts. Each person signs up, connects their own logins and uses their own AI app. Here's how to set a teammate up.

Plugsight doesn't have team accounts, shared workspaces or seats. Each Plugsight account belongs to one person, with its own connections, MCP servers, plan, Activity and settings. There's no way to invite someone into your account or to share connections between accounts.

So a teammate gets their own Plugsight account and connects the accounts they use, signed in as themselves. This guide walks through it.

Why separate accounts

  • Each person works as themselves. A teammate who connects Zendesk signs in to Zendesk with their own login, so their replies appear in Zendesk under their name, with their Zendesk role's permissions.
  • Each person approves their own changes. Approvals happen in the chat of the person whose AI app made the request.
  • Each person's Activity is their own. You see what your AI did; they see what theirs did.

Don't share your Plugsight password, and don't give a teammate an API key to your MCP server so they can use your accounts. An API key works for anyone who has it, and everything they do happens on your account and appears in your Activity. See Keep app passwords and API keys safe.

An AI app that connects with a sign-in window has to sign in to the Plugsight account that owns the MCP server. If your teammate tries to add your server's link to their AI app and signs in as themselves, they see "This connector points at an MCP server that isn't in your account."

Step 1: your teammate creates an account

  1. They go to app.plugsight.app and sign up with their own work email. They can use a password, an emailed sign-in link, Google or Microsoft. See Sign in to Plugsight.
  2. If they signed up with a password, they confirm their email. See Confirm your email.

Step 2: they choose a plan

Each account has its own plan. A new account starts on Free (2 connections, 1 MCP server, no marketing connectors, no sending or changes). If your teammate needs marketing data or changes, they upgrade on their own Billing page. See Plans.

Step 3: they connect their own accounts

On Connections → Add connection, they connect what they use, signing in as themselves:

  • Their own mailbox and calendar.
  • Shared tools such as Zendesk, Google Ads or GA4, with their own login. For Google services, their Google login needs access to the account first: you or an admin add them in Google Ads, GA4 or Search Console as usual.
  • Stores such as WooCommerce, with their own WordPress login (administrator or shop manager).

The same Zendesk, ad account or store can be connected by several people, each in their own Plugsight account.

Step 4: they create an MCP server and add it to their AI app

  1. On MCP servers, they click Create MCP server, name it and pick its accounts. See Create an MCP server.
  2. They add its Server URL to their own AI app (their own Claude or ChatGPT login) and click Allow access. See Connect AI apps.

Step 5: agree on safe defaults

Suggest your teammate starts with:

  • Every account switch off (Drafts only or Read-only), which is how new accounts start. Turn on only the ones they need to change.
  • Allow changes unticked on any server they only use for reporting.
  • A habit of checking Activity once a week. See Review Activity regularly.

Share these guides with them: Questions to try first and Write better questions.

When a teammate leaves

Their Plugsight account is theirs, so you can't remove it from yours. Instead:

  • Remove their access in the shared tools themselves (Zendesk, Google Ads, GA4 and so on), as you would for any leaver. Their Plugsight connections to those tools then stop working.
  • Ask them to delete their Plugsight account, or to remove the work connections from it. See Delete your account.
  • If you ever gave them an API key, revoke it on your server's page.