Teams & org chart
Model who reports to whom; it's what manager scoping, goals and digests key off.
A team is the unit of management in RepCue. It decides which calls a manager can review, whose numbers roll up into their dashboard, whose goals they can set, and what their weekly digest covers.
Creating a team
Settings → Teams → New team. A team has a name, a manager, and members.
The manager field is the load-bearing one: it is what grants that person read access to the team's calls, deals and analytics. A team with no manager assigned is just a grouping: nobody gains visibility from it.
- Admins create teams, edit them, and assign managers and members.
- Managers can see the teams they own, with member counts.
A person can manage several teams; their dashboard shows the union. Members belong to one team.
What changes once teams exist
Until you create a team, managers fall back to org-wide read access (a documented fallback), so a new workspace isn't an empty console on day one.
The moment a manager owns a team, that fallback ends: they see their teams and are refused scope=org. Modelling the org chart is therefore the action that turns RepCue from "everyone sees everything" into real internal access control. Do it before you invite the second team.
Teams also drive:
- Goals: set a target for a whole team at once (Goals & targets).
- Digests: a manager's weekly email covers their teams (Notifications & digests).
- Policies: consent, recording, language and coach-alert thresholds can differ per team (Per-team policies).
- Scorecard templates: a team can be graded on its own rubric (Coaching & scorecards).
Direct reports
users.manager_user_id records who a person reports to, independently of team membership. It is set from the People screen or pushed from your directory.
SCIM: your IdP already knows this
If you provision users over SCIM, RepCue reads your groups as the org chart, with no second setup.
- Groups named
admins,managersorrepsmap to a role. - Any other group becomes a team, with its memberships: "Enterprise West", "SMB Team", "EMEA".
Team group ids are namespaced team_<uuid> so the two kinds of group cannot collide. An IdP admin who already models sales teams in Okta or Entra gets RepCue read scoping for free.
Removing someone from a group removes them from the team. Deleting a user over SCIM deactivates them rather than destroying their history: call records and coaching artifacts survive, which is what an audit expects.
Details in SSO & SCIM.
API
GET /v1/teams, POST /v1/teams, GET|PATCH|DELETE /v1/teams/:id, POST /v1/teams/:id/members, DELETE /v1/teams/:id/members/:userId.