1
Prepare your team seats
Open Team → Manage seats to purchase seats for your team. Members can keep their existing coding-assistant subscriptions when using Edgee.
2
Invite the pilot members
Open Team, invite the members, and select the appropriate roles. They must accept their invitations using the invited account. Give administrator access only to people who need organization-wide controls.
3
Connect each agent
Share the agent quickstart. Each member signs in, selects your organization, and launches an agent. Confirm the agent appears under that member and makes at least one request.
4
Create a squad
In Team → Squads, create a squad such as
Platform and add the pilot members. Check membership and inherited settings before saving. See Squads.5
Apply a routing strategy
Create a Strategy, then assign it to the squad. Choose the budget amount, period, and whether it is shared or per member. A saved strategy does not change traffic until it is assigned.
6
Choose a cap and an alert
For the strategy-assigned squad, use Block at 100% if requests must stop at its budget. Do not add a hard usage limit to the same scope. For scopes without a strategy, use a usage limit. Configure an alert for an eligible usage limit or the organization credit balance.
7
Verify as a member
Have a pilot member launch a new session. In Logs, confirm the served model and provider match the effective settings. In Team, verify member attribution. Check that the member can see their own usage and understands any locked settings.
Before expanding the rollout
- Each pilot member has accepted the invitation and selected the right organization.
- Their sessions and costs are attributed to the expected member and squad.
- Each member has the seat needed for team features.
- The strategy is assigned and its effect has been checked on a real request.
- Someone owns the alert notifications and knows how to investigate a blocked request.