Understand a team and its members
Find a team, inspect its roster and captured activity, and distinguish membership from reporting relationships and edit authority.
Reporting relationships, Team membership and configured limits describe different things. Use this guide to inspect the directory subject before configuring a control.
Before you begin
Confirm the organization and reporting range. Your role and visibility determine which records you can inspect. A manager relationship or Team membership does not grant budget-edit permission; check Roles and visibility before editing.
Find a team in the list
- Open Teams with View: Roster and search for the team.
- Select its row to inspect membership and captured activity beside the table.
- Confirm the reporting range before comparing spend. A team with no configured budget is different from one with no captured activity.
Inspect the member table
- Open the selected team's roster and select a member.
- Review that person's memberships, captured spend and last captured activity for the selected range.
- Open Manage budgets, Set rate limits or Restrict access to inspect the corresponding control's subject and filters.
Unknown spend and No captured data do not mean zero usage. Check capture coverage and the reporting range. A member can match an organization limit, a Team limit and a direct Member limit; panel order does not establish precedence.
Directory tree view
Use Directory with View: Tree to explore reporting relationships, then open a team or member record for its membership and configured controls.
Explore reporting relationships
Expand a manager's branch and select a person.
The Manager column and indentation show recorded reporting relationships. Captured sessions, Estimated spend, 30D and Activity, 7D use their labeled windows; captured spend and a daily cap cover different periods.
Compare team membership and activity
The Teams roster shows member counts and captured activity. Open a selected team's members to inspect individual memberships.
A person can belong to multiple Teams. A Team budget applies its actual membership and exclusions; it does not exempt members from organization controls or another matching rule.
Reporting, membership, and limits
| Relationship | Meaning | Boundary |
|---|---|---|
| Reporting relationships | Recorded manager relationship, with its source and resolution state | Does not create a budget or grant edit permission |
| Team membership | People listed as members of that Team | Can overlap; membership is not a money allocation |
| Configured limits | Budget records with their own scope, conditions and exclusions | Apply according to configuration, not chart position |
Confirm the directory source and update process for the deployment. For Okta, configure SCIM provisioning and verify membership. After an update, verify the roster and assigned roles; keep unresolved or conflicting reporting data unresolved.
Troubleshooting
| Symptom | Next action |
|---|---|
| A person belongs to more than one Team | Inspect each membership and matching control. Do not add overlapping Team totals into an organization total. |
| Spend is Unknown or activity is missing | Check the reporting range and capture coverage rather than treating missing data as zero. |
| Reporting relationships are unresolved | Confirm the directory source and its update process. Leave conflicting relationships unresolved. |
| Edit budget is disabled | Check Admin access and confirm that the selected record is editable. |