Understand Triple Session’s seat types (Viewer, Recording), user roles (Member, Manager, Admin), and analytics visibility to control access, credit usage, and reporting across your organization.
Triple Session controls access with three independent settings: Seat Types (can they record and use credits), User Roles (what they can see and manage), and Visibility (whether they appear in team reporting). Set all three when you invite a member or change them anytime after.
A user’s Seat Type determines whether they can record meetings and consume credits from your organization’s shared pool. Credits are managed at the company level — there is no individual credit limit.
Seat Type
What they can do
Consumes credits?
Viewer Seat
Access AI Coach, view calls and data (based on their User Role)
No
Recording Seat
Record meetings, upload call files, import from integrations (Google Meet, Zoom, Aircall, HubSpot, Fireflies)
Yes — from the company pool
A Viewer Seat cannot record or upload calls regardless of User Role. This seat type is typically assigned to managers and admins who need oversight without contributing their own call recordings.
Add-ons provide extra functionality tied to a user’s seat type.
AI Coach Bot: available exclusively for users with a Recording Seat. To enable this add-on for a user, contact the support team at support@triplesession.com.
A user’s permissions come from their role. Member and Manager are workspace roles — every user is one or the other. Admin is a separate company-level role that can be granted to any user, whether they’re a Member or a Manager, adding company-wide settings on top of their workspace role. (Seat Type, not role, determines whether they can record.)
A company-level role layered on top of a user’s Member or Manager role. It adds permissions for company-wide settings and integrations — it does not change their workspace access.
Permission
Details
Manage integrations
CRMs (e.g., HubSpot) and Aircall
Map CRM fields
Map CRM fields with scorecards
Manage automations
Company-wide automation rules
Admin only covers company-wide configuration. A user’s workspace access — viewing calls, managing the team — still comes from their Member or Manager role. For example, a Member who is also an Admin can manage integrations but still only sees their own calls.
Visibility controls whether a member appears in team-level reporting. It is separate from Seat Type and User Role: a member can have full access to their own calls while staying out of shared metrics. Use Hidden for non-selling managers, sales ops, or admins who review calls but should not skew team performance data.
Visibility
Where the member appears
Visible
Analytics and Scorecard breakdowns, daily and weekly digest emails, leaderboards, and the members filter on the meetings page and in Moments
Hidden
Excluded from all of the above
Hiding a member does not block their access to calls via a direct link. Visibility only controls whether their data appears in shared analytics views.
Set visibility when inviting a member (the Visibility column) or change it later from the Members table. For the step-by-step, see Manage Members.
Visibility is distinct from meeting access (who can open a recording or AI report). To control access to recordings, see Privacy Settings.
