Teams
Collaborate in Invoked — share skills across your team, see team-wide analytics, and manage members, all while credentials stay local to each machine.
A team in Invoked lets a group of people share what they build — skills, and the insight from team-wide analytics — while every person's API keys and sensitive data stay on their own machine.
Teams are available on the Team plan. A solo or trial user has no team; the moment you're on a team, Invoked becomes collaborative without giving up its local-first guarantees.
What's shared vs. what stays local
| Shared with the team | Stays on your machine |
|---|---|
| Skill definitions (name, tools, prompt, examples) | API keys & personal access tokens (OS keychain) |
| Team-wide usage analytics (aggregate) | Your run history content (prompts, outputs) |
| Team membership, roles, seats | Your local configuration |
The rule of thumb: definitions are shareable, credentials never are. A skill you share carries the recipe, not the keys — each teammate supplies their own.
Telling team assets apart
Anything shared with your team is marked with a Team badge so you can tell at a glance what's yours versus your team's:
- A shared skill shows a "Shared" badge, plus who shared it and when.
- The dashboard shows a "Team" badge when you're viewing team-wide stats.
- Team runs are marked in Run History.
Your team context
Your current team appears in the user menu at the bottom of the sidebar. If you belong to more than one team, you can switch between them there — switching changes which shared skills and which analytics you see.
Roles
| Role | Can do |
|---|---|
| Admin | Invite/remove members, change roles, rename the team, manage the subscription |
| Member | Use shared skills, see team analytics, share their own skills |
A team always has at least one admin — Invoked won't let you remove or demote the last one.
Next steps
- Set up & manage your team — invites, roles, seats
- Share skills with your team — the day-to-day workflow