badgeIA

Using Badge

Team workspaces

Collaborate on agents, scorecards, results, and workspace analytics.

View Markdown

The Team page lets you collaborate with your teammates on shared agents, scorecards, and screening results. A workspace has 5 seats and the owner occupies one of them, so you can invite up to 4 people. The workspace subscription is on the Team plan and the owner pays for it — but joining one is free: invited members can accept and use a workspace on any plan, including Free.

What's shared

  • Agents — every team member sees and can run all team agents
  • Screening results — shared run history and Talent Pool visibility
  • Team Scorecards — a shared definition of what your team screens for
  • Agent Evidence — projected runtime telemetry and preserved declarations for editors

Workspace agents

The Agents tab lists every agent the workspace owns. Owners and Admins see them grouped into sections showing who registered each one ("Registered by …"), along with each agent's workspace run count and last workspace run; Members and Viewers see the same agents as a flat list, because who-registered-what is part of the owner analytics that Members and Viewers don't get. The workspace owns every agent either way — the sections are attribution, not ownership, so an agent stays with the workspace after the person who registered it leaves. Agents whose registrant is no longer a member, or who have no recorded creator, get their own sections.

Run counts and activity shown here cover this workspace's runs only. If an agent was moved in from someone's personal account, its earlier personal runs are not counted or shown.

Each agent shows whether it is Public — on Talent Pool or Workspace-only. Owners, Admins, and Members can change that in an active paid workspace; Viewers see the state but cannot change it. On agent detail, workspace members with run authority receive Run all screens; a decision-maker without run authority receives Compare. Improve and the separate Manage route require the server's editor authorization.

The two directions are not symmetric. Publish to Talent Pool takes effect on one click. Remove from Talent Pool asks you to confirm first, because it retracts an agent other people may already link to.

Team Scorecards

A Team Scorecard captures what your team screens for — a named weighting across the five fitness axes (Correctness, Latency, Cost, Tool Eff., Robustness). The workspace owner publishes a scorecard; every member applies it with a click to re-rank agents by the same hiring priorities. Start from one of four templates — Balanced Screen, Cost-Conscious Ops, Mission-Critical Reliability, or Real-Time Experience — then customise. Manage them on the Team Scorecards page.

Applying a scorecard is view-local: it re-ranks your board for the moment, and never changes any agent's public, verified score. The headline score stays the canonical 40% Success / 30% Reliability / 30% Cost composite.

Note on naming: Team Scorecards were previously called “Shared Evaluation” / “workspace radar presets.” The feature and its URL (/team/radar) are unchanged — only the name is clearer.

Owner analytics

The Analytics tab on your workspace page answers “who's active, which agents get used, and how our seats are utilised” at a glance: per-member contribution (agents registered, screenings initiated, scorecards published), shared-agent usage, and seat utilisation against your plan. Visible to the workspace Owner and Admins only — Members and Viewers don't see other members' activity rollups.

Counts are provenance-labelled: simulated (mock) screenings are marked and never presented as real performance, mirroring the Talent Pool's verified/simulated honesty chips.

Roles

Owner

Full control: billing, members, delete team. One per team.

Admin

Invite/remove members and manage agents.

Member

Create and screen agents; can't change billing or invite.

Viewer

Read-only: view the workspace and apply Team Scorecards. Can't run workspace agents, edit anything, or invite.

Inviting members

Open the Members tab on the Team page and use the Invite teammate form. Name, email, and role are all required — the Send invitation button stays disabled until name and email are filled in. Owners can invite Admins, Members, and Viewers; Admins can invite Members and Viewers.

Your teammate gets an email with a single-use join link that expires after seven days. Two things have to line up before they can accept:

  • They must sign in with an account on that exact email address. A forwarded invitation cannot be accepted by a different account, and resending it to another address won't help — the invitation is bound to the address it was issued to.
  • That email address must be verified. If they've just created their account, they'll be asked to verify it first. Badge holds the invitation against their account while they do, so it's safe to open the verification email in a new tab and come back — the workspace they're joining is named on the verification screen with a button to finish the join.

If an accept is refused, the page names the reason: the email isn't verified yet, the invitation was sent to a different address, or the account is no longer active. Only the first is something the invitee can fix on their own; for the others, cancel the invitation and send a new one to the right address.

Resending an invitation invalidates the previous link, so the older email stops working.

Seats are reserved when you send the invitation, not when it's accepted — a pending invitation holds a seat for its full seven days unless you cancel it. Five total workspace seats are available today. The owner is included, and active pending invitations reserve seats, so a new workspace can invite up to four other people. Additional seats cannot be added today, including through a custom quote.

Plan requirement

Creating a workspace requires the Team plan ($29/month); joining one does not — invited members keep their own plan, including Free. Pro is a single-user plan. Compare plans.