Overview

This feature is designed to support clients where the same back-end administrative staff support multiple credentialing Boards or organizations.

This approach reduces the administrative burden on that staff by:

• Granting administrative users a single set of credentials to manage

• Allowing common configuration elements (like Workflow design) to be shared between Boards

• Avoiding the need to manage multiple LearningBuilder instances

Features of the Multi-Tenant Architecture

In a multi-tenant configuration:

• Each Tenant has a dedicated URL and logo

• Content Blocks can have Tenant-specific content

• Email Templates and Workflows can reference Tenant-specific variables

• Credentials can be associated to specific Tenants

• Tenants can have separate https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/521306131

• Tenants can have separate Payment Gateway configurations (for specific payment processors only)

Reasons to Consider a Multi-Tenant approach

Customers who have a single administrative staff but will be managing multiple external boards ought to consider a multi-tenant approach. For this approach to work, customers will need to accept the following approach:

• Client manages multiple Boards with the same back-end staff

• Administrators can access Practitioner data from all Tenants

• All payments will be managed using the same payment gateway (though in some cases there may be Tenant-specific account details)

• Communications will all be sent from the same Reply To and From addresses

A multi-tenant approach is not suggested when:

• Programs have data segmentation restrictions that prevent them from operating in the same environment

• Shared Activity Workflows must act differently across Tenants.