The team portal
A two-page view of a team's token consumption and membership, for deployments licensed by team rather than by company.
Teams versus organizations
CADCoPilot has two ways of grouping people. An organization is the normal one: it owns the licence seats, the messaging channels, the connections and the knowledge base, and its members use the organization portal. A team is a lighter grouping with its own subscription and token limit, used on team-plan and older deployments.
Teams are created and listed by a website admin on Admin portal → Teams. The two pages described here are the team-facing view of that same data and live in the admin portal's URL space:
- Team Dashboard —
/admin/team/dashboard - Team Members —
/admin/team/members
Reach them by signing in at /admin/login. They are not in the admin sidebar; open the URLs directly or follow the help icon on the page you are already on.
Team Dashboard
Admin portal A read-only overview of the current month.
- Stat cards — the team name, member count against the plan's seat maximum, tokens used this month and the plan type. A missing plan shows as a dash rather than an error.
- Token usage this month — a progress bar shown only when the subscription has a monthly token limit. It turns amber above 75 % and red above 90 %. An unlimited plan simply has no bar.
- Member activity this month — every member with their role, tokens and session count, heaviest user first.
Everything counts from the first of the current UTC month and resets when the month rolls over, so a low figure early in a month is normal rather than a sign that logging stopped.
Team Members
Admin portal The team's roster, with this month's tokens per person.
Adding someone
- Press + Invite Member and enter the person's email address.
- Press Add. The account must already be registered — this button links an existing user to the team, it does not create an account or send an email. An unknown address is refused with “User not found”.
- If the team is already at its seat maximum you get “Team is at max capacity”. Raise the seat count on the team's subscription first (Admin portal → Licenses).
- Adding somebody who is already on the team is refused with “Already a member”.
New members join with the member role. The team's own admin is set when the team is created and has no Remove button here, which prevents a team from being left without an owner. Removing a member takes effect immediately and only detaches them from the team — the user account, their chat history and their personal AI key are untouched.
Common mistakes
- Expecting an invitation email. The team invite dialog links an existing account. Real email invitations for a company are sent from the organization side — see Admin portal → Org Members in the Website Admin Portal guide.
- Reading the dashboard as a licence check. Seats and plan come from the team's subscription; entitlement questions belong on Licenses.
- Looking for knowledge, channels or connections here. Those are organization-level features and live in the organization portal.
See also
- Web Portal Overview
- Website Admin Portal — Teams, Licenses and Usage.