Skip to content

Licensing overview

MiaRec capabilities are licensed per user as seats. This page explains the license model and — because licensing information is spread across three places in the product — where each piece lives.

Seat types

Five license types are assignable to users. The UI shows each with a short code:

UI label Code What it entitles
Call recording license REC The user's conversations are captured by the recorder
Screen recording license SCR The user's desktop is captured during conversations
Live monitoring license MON The user's active conversations can be listened to in real time
Agent evaluation license EVAL The user's conversations can be evaluated manually (QA)
Speech analytics license SPCH The user's conversations are transcribed and analyzed by AI

Label renames in progress

The display names "Agent evaluation license" and "Speech analytics license" correspond to the Quality Assurance and Conversation Analytics products. This guide uses the current UI labels in procedures; the codes (REC/MON/EVAL/SPCH/SCR) are identifiers and do not change.

Besides the five seat types, the recorder license can carry recording session and monitoring session entitlements — concurrency pools counted per simultaneous conversation rather than per user. They are not assignable to users.

Where licensing is enforced

A seat gates its stage of the pipeline: capture requires a recording seat; transcription and AI tasks run only for users with a speech analytics license; manual evaluations require the evaluated user to hold an agent evaluation license; live monitoring requires a monitoring seat; screen capture requires a screen recording seat. Auto QA is driven by the AI pipeline and therefore follows the speech analytics license, not the evaluation license.

Licenses and packaging

Commercially, customers subscribe to the MiaRec products — Conversation Analytics and Quality Assurance (see Subscriptions & Licensing for the customer-facing framing). In the product today there is no package-level switch: a subscription is realized as a combination of license seats, role permissions, and feature flags. When you onboard a customer, you translate their subscription into per-tenant license limits and, where applicable, flags — see Onboarding a tenant.

The three places licensing lives

What Where Documented in
License keys — the system-wide entitlement pools issued to your recorder and screen-recording modules Administration › Licensing › Recording License / Screen Recording License License keys
Per-tenant limits — how many seats of each type a tenant may consume Tenant page › License limits Tenant configuration
Per-user assignment — which users hold which seats Each user account (or auto-provisioning) Customer side: User accounts

Usage across all three is summarized on the License usage page — see License usage. A tenant with no limit set for a type shows No limits and draws dynamically from the system-wide pool.