# White-Label Telehealth Platform | MedConnect

> Deploy MedConnect under your identity with a private domain, customer logos, patient landing page, link copy, email sender identity and configured authentication screens.

[Home](/ar)/ [Platform](/ar/software/telehealth-platform)/ White-label deployment
Your service. Your identity.

# A white-label telehealth platform

MedConnect can be provisioned under your organization’s identity: private domain, logos, patient landing page, link copy, email sender identity and authentication screens. Our team configures these elements as part of the deployment.
[Scope your deployment](#white-label-scope) [View the patient portal](/ar/software/patient-portal)    [Image: CUBESANTÉ white-label patient access interface on MedConnect] CUBESANTÉ · real customer-identity deployment example
Configuration scope

## The touchpoints that can carry your identity

The exact scope is confirmed during discovery. It separates deployment identity, establishment branding and patient-portal functionality.
01
### Private domain

A customer-facing domain can be provisioned for the deployment.
02
### Logos and visual identity

Customer logos can appear across supported user-facing surfaces.
03
### Patient landing page

The public page can use supported colors, content and calls to action.
04
### Link-sharing copy

Patient-link messaging can be adapted to the customer context.
05
### Email sender identity

A customer email sender domain can be configured as part of the project.
06
### Authentication screens

Customer authentication themes can be created and deployed by our teams.
07
### Supported emails and reports

Establishment logos can appear in generated emails and reports that support this identity.

Deployment method

## A controlled configuration, not a theme editor

Our team assembles the identity assets, domains and supported screens, then validates them with the customer before go-live.
- **01 · Discovery**Identify brands, establishments, domains, languages and affected journeys.
- **02 · Identity kit**Collect logos, colors, copy, sender identities and usage rules.
- **03 · Provisioning**Configure the agreed domains, public pages, emails and authentication themes.
- **04 · Acceptance**Validate journeys, links, emails, reports and responsibilities before launch.

Deployment identity

## Domain and authentication

Customer domains, sender identity and authentication themes are manually provisioned according to the approved scope.

Patient experience

## Purpose-built public page

The public landing page can use supported logos, copy and colors. Authenticated screens are not represented as fully customizable.
[Explore the patient portal →](/ar/software/patient-portal)
Clinical system

## Software and interoperability

Branding wraps the service. Devices, modules and interfaces with third-party systems remain configured and validated as a clinical project.
[View the complete platform →](/ar/software/telehealth-platform)
## What “white-label” means here

It is a configuration service attached to a MedConnect deployment. It is neither a self-service portal builder nor a promise that every screen and message can be changed without scoping.

### Scoped with the deployment

Identity, domains, supported surfaces, languages, responsibilities and acceptance criteria.

### Configured separately

Patient functions, clinical modules, devices, hosting and interoperability.

## Frequently asked questions
Is MedConnect available as a white-label telehealth platform?
Yes. MedConnect can be deployed with a private domain, customer logos, a patient landing page, tailored link copy, customer email sender identity and configured authentication screens.
Is white-label customization self-service?
No. White-labeling is a configured service provisioned by the MedConnect team during implementation.
Can every authenticated portal screen use custom colors?
The verified color customization applies to the public patient-portal landing page. It should not be represented as global color customization across every authenticated interface.
Does white-labeling change the clinical functionality?
No. Customer identity wraps the deployment, while clinical modules, connected devices and integrations are configured and validated separately.

Project scoping

## Define your deployment identity

Tell us about your brands, domains, establishments, languages and patient journeys. We will confirm the supported surfaces and provisioning plan.
[Deployment guide](/ar/telehealth-deployment-guide) [Offers and pricing](/ar/pricing)       الاسم       البريد الإلكتروني *      الهاتف       الرسالة        Request project scoping  تم إرسال رسالتك بنجاح، وسنعود إليك في أقرب وقت ممكن.   حدث خطأ! هل قمت بملء جميع الحقول؟