Team Configuration

One admin configures. The whole team stays in sync.

Team Configuration lets an administrator export a single configuration file and share it with the entire team via a URL. Shared config covers Quick Searches, Response Repo entries, Context AI prompts, Note Clipper targets, Autolinker rules, playbooks, and lookups. Extensions refresh automatically every 4 hours — no backend, no IT project.

Admin Workflow

1. Configure the extension

Set up the extension exactly as you want your team to have it.

2. Export

Open Options → Home, scroll to Team Configuration, and click Export Team Config. A team-config.json file downloads. Optionally include API keys — only if the config URL will be private.

3. Host the file

• GitHub Gist (secret) — best for small teams without sensitive data. Create a secret Gist, paste the file, use the Raw URL (from gist.githubusercontent.com), trimmed of the SHA segment so it stays stable across edits.
• Private GitHub repo + token — best for mid-size teams. Generate a fine-grained personal access token with read-only Contents permission scoped to the config repo. Raw URL format: https://raw.githubusercontent.com/{user}/{repo}/{branch}/team-config.json
• Internal intranet URL — recommended for enterprises. Host on your intranet, SharePoint, or file server with the header Access-Control-Allow-Origin: *.

4. Share the URL

Distribute the config URL (and access token, if using a private repo) to the team.

Lock Behavior

Admins can lock individual products so only managed items appear — Quick Search, Response Repo, Note Clipper, Autolinker — or lock Context AI's provider and key while still letting users add their own prompts. Unlocked products show managed items first, then personal items.

Disabling Products

Admins can fully disable a product for the whole team — for example, Context AI until leadership approves an API key policy. Check the product under Disable products for team users before exporting. Disabled products disappear from every user's menu and show a banner with your reason on their options page. Personal data is preserved and restored when you lift the block.

Updating

Edit your configuration, export again, replace the hosted file. Team extensions update within 4 hours, or immediately via Refresh Now.

User Workflow

1. Open Options → Home → Team Configuration.
2. Paste the admin-provided URL and click Connect.
3. The extension confirms with the organization name and sync time.

To disconnect, clear the URL field and click Connect — managed items disappear and personal configuration returns.

Troubleshooting

• Failed to fetch / 401 — verify the URL form for your hosting option; for Gists confirm you used the Raw URL; for private repos confirm the token hasn't expired and is SSO-authorized; for intranet URLs confirm VPN and the Access-Control-Allow-Origin header.
• "URL did not return valid JSON" — you likely used the Gist page URL instead of the Raw URL.
• Config not updating — confirm the hosted file actually changed, then click Refresh Now.
• Managed items not appearing — reload the extension from chrome://extensions and reconnect.