Skip to main content
Before diving into specific features, it helps to understand the foundational concepts that shape how Regentra works. These patterns repeat throughout the platform.

​
Multi-Tenant Architecture

Every organization in Regentra is a fully isolated tenant. Data, configurations, controls, policies, and user access are all scoped to a single organization. MSPs operate across multiple tenants. As an MSP, you can:
  • Create and manage client tenants from your MSP dashboard
  • Assign technicians and compliance officers to specific client organizations
  • Switch between client tenants without logging out
  • Maintain separate compliance programs, SLA policies, and configurations per client
There is no data bleed between tenants. A control, policy, or ticket in one organization is never visible to another.

​
Common Control Framework (CCF)

The Common Control Framework is Regentra’s internal mapping layer. Instead of duplicating effort across frameworks, the CCF lets you implement a control once and satisfy requirements across multiple standards. For example, an “Access Control Policy” might map to:
  • HIPAA § 164.312(a)(1) — Access Control
  • SOC 2 CC6.1 — Logical and Physical Access Controls
  • NIST CSF PR.AC-1 — Identities and credentials
  • ISO 27001 A.9.2.1 — User registration and de-registration
When you update the status or evidence for that control, it reflects across every mapped framework simultaneously.
The CCF is what makes multi-framework compliance manageable. Adopt three frameworks and you will not triple your workload — overlapping controls are consolidated automatically.

​
Frameworks

A framework is a compliance standard you can adopt within your organization. Regentra supports HIPAA, SOC 2, NIST CSF, ISO 27001, CMMC, PCI-DSS, GDPR, and FTC Safeguards. When you adopt a framework:
  1. The full control set is seeded into your organization
  2. Controls are mapped to the CCF
  3. Gap analysis becomes available on your dashboard
  4. Framework-specific features unlock (e.g., BAA tracking for HIPAA)
You can adopt multiple frameworks. Unadopting a framework removes it from your active view but does not delete underlying control data.

​
Policies and Campaigns

Policies are formal documents (e.g., Acceptable Use Policy, Incident Response Plan) that your organization maintains for compliance. Campaigns are the mechanism for distributing policies to employees and collecting signed acknowledgments. When you create a campaign:
  • Select the policy and the target audience
  • Employees receive a notification to review and sign
  • You can track completion rates and send reminders
  • Signed records are stored as compliance evidence

​
SLA Policies

An SLA policy defines response and resolution time targets for support tickets based on priority level. SLA policies account for:
  • Business hours — so timers pause outside working hours
  • Priority tiers — different targets for Critical, High, Medium, and Low
  • Escalation rules — what happens when a target is about to be breached
SLA policies are assigned at the organization or client level.

​
Portal

The Portal is a customer-facing interface where your clients can:
  • Submit and track support tickets
  • Access the knowledge base
  • Engage in live chat with your team
  • View compliance status dashboards (if enabled)
The portal supports branded login pages with your logo and colors. Each client tenant can have its own portal URL.

​
Roles

Regentra uses role-based access control to manage permissions across the platform.
Platform-level access. Can manage all organizations, system settings, and global configurations. Reserved for Regentra platform operators.
Full access to a single organization. Can manage users, settings, integrations, and all modules.
Manages the MSP relationship layer. Can create and manage client tenants, assign technicians, and oversee cross-tenant operations.
Full control over the compliance module. Can adopt frameworks, manage controls, create policies, and generate reports.
Works within the compliance module. Can update control statuses, upload evidence, manage policies, and run assessments.
Limited access. Can view assigned policies, sign acknowledgment campaigns, and submit basic information.
View-only access across all modules. Cannot modify any data. Useful for auditors or executive stakeholders.
Focused on PSA operations. Can manage tickets, track time, update assets, and access the knowledge base. No compliance module access by default.
Users can hold different roles in different organizations. An MSP technician in one tenant can be a compliance officer in another.