What the team shares
- Integrations. The tools members build belong to the team, which chooses whether each integration is private or public; see integration MCPs.
- Saved logins. A team keeps several logins per website, each with its own access list; see share a login.
- Usage. Every member draws on one pool of tool runs and builds; see plans and limits.
Members
Each person signs in to Pomerado with their own identity and has one role: Owner, Admin or Member; see roles and invitations. A person belongs to at most one team and can keep a Personal account beside it. Logins in that Personal account are never shared with the team automatically. Each API key and each MCP connection belongs to one account, chosen when it is created.Manage the team
The Dashboard’s Team page lists members, pending invitations and roles. Every member can see the member list. The API has the same operations under/v1/team.
See each member’s usage
The Dashboard’s Usage page shows the team’s allowances and this month’s usage by member. From the API,GET /v1/usage with group_by=member adds each member’s tool runs and integrations created. Owners and Admins see every member; a Member sees only their own row.
Details
Details
- When a member is removed, their running jobs stop and their API keys stop working. The logins they created stay with the team.
- An Owner or Admin can delete the Business account from Dashboard Settings. This signs everyone out and deletes the team’s logins, integrations, webhooks and usage.