Skip to main content

Understanding users roles and permissions

Lais Lara avatar
Written by Lais Lara
Updated over a week ago

Understanding Seat Types and User Roles concepts is key to managing your team's access and credit consumption effectively.

With our latest update, we have moved credit management to the company level. This means credits are no longer assigned to individual users but are instead shared from a central company pool. To facilitate this, we have introduced Seat Types.

Seat Types

A user's Seat Type determines whether or not they can record meetings and consume credits from the company's shared pool.

There are two types of seats in Triple Session:

  • πŸ‘€ Viewer Seat: for users who only need to review calls, dashboards, and analytics. This seat provides view-only access and does not consume credits.

  • πŸŽ₯ Recording Seat: for users who need to record, upload, or import meetings. This seat type consumes credits from the organization's pool.

πŸ‘€ Viewer Seat

This seat is designed for users who need to review calls and data but do not need to record their own meetings.

  • Can access AI Coach and view calls and data, depending on their User Role permissions.

  • Does not have access to record or upload calls.

  • Does not consume credits from the company pool.

πŸ’‘ Typically assigned to managers and admins who need oversight without contributing their own call recordings.

πŸŽ₯ Recording Seat

This seat is for active team members who need to record, upload, or import their calls for analysis.

  • Can record meetings, upload call files, or import from third-party integrations (e.g., Google Meet, Zoom, Aircall, HubSpot, Fireflies).

  • Consumes credits from the shared company credits pool.

  • There is no individual credit limit; usage is drawn from the company's total available credits.


✨ Add-ons

Add-ons provide extra functionality and are associated with a user's seat type.

  • AI Coach Bot: an add-on that can be enabled for any user who has a Recording Seat.

To enable the AI Coach Bot add-on for a user, please contact our support team at [email protected].


User Roles

A User Role defines a user's permissions and what they are allowed to see and do within the platform.

The user's assigned Seat Type determines if they can perform recording actions.

πŸ‘€ Member

The standard permission level for most users.

  • Can upload calls manually (if they have a Recording Seat)

  • Can have calls reviewed automatically (if they have a Recording Seat)

  • Can connect with Call Recording Tools (if they have a Recording Seat)

  • View and search their own meetings and moments.

  • View their own scorecards

  • Change their scorecard for their calls

  • Can delete their own calls

  • Can enable/disable their own smart scorecards

πŸ“Š Manager (Workspace Admin)

This role is for team leads or managers who need oversight of their workspace.

  • ‴️ Inherits all Member capabilities.

  • View workspace analytics and access all calls in the workspace.

  • Can change the scorecard for any call in the workspace.

  • Can delete any call in the workspace.

  • Can invite and remove members from the workspace.

  • Can add/remove users from Analytics and meeting lists.

  • Can update users' smart scorecards and call recording configurations.

πŸ”‘ Admin (Company Admin)

The highest permission level, intended for managing company-wide settings and integrations.

  • Can manage company-wide integrations like CRMs (e.g., HubSpot) and Aircall.

  • Can map CRM fields with scorecards.

Here's how to manage your team's seats

  1. If you are an admin, navigate to the People page under the Organization section

  2. Find the Seat Type column

  3. Click the dropdown

  4. Assign the person a new seat

  • πŸŽ₯ Recording Seat: Select this for users who need to record, upload, or import meetings. This seat type consumes credits from the organization's pool.

  • πŸ‘€ Viewer Seat: Select this for users who only need to review calls, dashboards, and analytics. This seat provides view-only access and does not consume credits.

Did this answer your question?