Summary

Call visibility in Hyperbound is controlled by each role group’s data-visibility setting and by the user’s position in the team hierarchy.

Visibility is not hard-coded by role. Admins or Owners configure what each role group can see from the workspace’s visibility settings.

🛠 Tools Required

• Hyperbound access
• Admin or Owner permissions to change workspace visibility settings

How Manager Hierarchies affect visibility

Under Manager Hierarchies, Hyperbound uses the team tree to decide which teams are included in a user’s visibility scope. Nested teams count as sub-teams of their parent team.

A user’s access comes from their Hyperbound role group, the visibility setting selected for that role group, and the team or teams they belong to.

Data visibility scopes

• All data — users can see calls across the entire workspace.

• Team + sub-teams — users can see their own calls, plus calls from members of their direct teams and any nested sub-teams.

• Direct teams only — users can see their own calls, plus calls from members of the teams they belong to directly. Nested sub-teams are not included.

• Personal only — users can see only their own calls.

Which scopes each role group can use

By default, role groups are set to All data unless an Admin or Owner changes the setting.

Important rules and exceptions

• Users can always see their own calls.

• Participants on a real buyer call can see that call.

• Private simulated calls are visible only to the person who created them.

• Folder and bot access are separate from call visibility. Folder sharing controls which training content users can access; data visibility controls which calls they can see.

📝 FAQ

• Review visibility settings whenever you change a user’s role or team assignment.
• If someone can’t see expected calls, check their role group’s visibility setting and their team placement.