---
title: "Multi-Brand: Managing Multiple Brands in DSR"
description: MineOS Multi-Brand allows large organizations to present each of their brands with a fully independent, branded experience to data subjects — including a dedicated Privacy Center, email communications, and visual identity. Behind the scenes, all DSR request handling, processing, and operations are managed centrally in MineOS in a single unified workspace, with the ability to filter, sort, and view requests by brand.
---

[Skip to content](https://docs.mineos.ai/knowledge/multibrand#main-content)

[![Mine](https://docs.mineos.ai/hs-fs/hubfs/Frame%201948756858.png?width=62&height=40&name=Frame%201948756858.png)](https://docs.mineos.ai/knowledge)

Open main navigation

Close main navigation

 Hello! How can we help you?

- There are no suggestions because the search field is empty.

1. [Help center](https://docs.mineos.ai/knowledge)
2. [DSR Handling](https://docs.mineos.ai/knowledge/dsr-handling)
3. [Processing Requests](https://docs.mineos.ai/knowledge/dsr-handling#processing-requests)

# Multi-Brand: Managing Multiple Brands in DSR

## MineOS Multi-Brand allows large organizations to present each of their brands with a fully independent, branded experience to data subjects, while all DSR request is managed centrally under a single workspace.

### **Overview**

**Plan availability**: Enterprise

MineOS Multi-Brand allows large organizations to present each of their brands with a fully independent, branded experience to data subjects — including a dedicated Privacy Center, email communications, and visual identity.

Behind the scenes, all DSR request handling, processing, and operations are managed centrally in MineOS in a single unified workspace, with the ability to filter, sort, and view requests by brand.

In addition, existing integrations continue to work without any changes, and the public API is fully backward compatible with an additional brand-id field. See more details on the API updates in the below API section.

**What's separated per brand (data subject-facing):**

- Privacy Center (dedicated URL, form, settings, custom code)
- Email templates and designs
- Email sender domains
- Brand visuals (logo, color scheme)

**What stays centralized at the company level:**

- Integrations
- Rights' workflows
- Request management
- Reporting

### **Key Concepts**

#### **Company vs. Brand**

Company and Brand are two distinct entities in MineOS. It's important to understand the difference:

|  | Company | Brand |
| --- | --- | --- |
| **Appears in** | Main Settings -\> General | DSR Setup -\> Brand details under each brand |
| **Name** | Read only | **External name** (shown to data subjects) + **Internal name** (visible inside MineOS only) |
| **ID** | Read only, immutable | Read only, immutable |
| **Logo** | Company logo | Brand logo |
| **Purpose** | Global account identity | Client-facing DSR identity |

**Note:** If you want to update what data subjects see in your Privacy Center, update the **Brand** name and logo — not the Company name and logo.

#### **The Default Brand**

The first brand created in an account is always the **Default Brand**. This cannot be changed.

**Default Brand rules:**

- Cannot be reassigned
- Always exists — cannot be deleted
- Used as the fallback in API calls when no `brand-id` is specified
- Displayed with a **"Default"** label in the UI
- For existing accounts, the default brand is automatically initialized with the company name and logo during migration

#### **Brand Fields**

| Field | Description |
| --- | --- |
| **Name** | External name shown in the Privacy Center and all end-user communications. Required. Editable. Max 50 characters. |
| **Internal Name** | Visible only inside MineOS. Optional. Editable. Must be unique within a company. |
| **Brand ID** | Auto-generated, immutable identifier. Read only. Used in API calls and integrations. Can be copied to clipboard from the brand page. |
| **Brand Logo** | Displayed in the Privacy Center and email communications. Can be uploaded and updated at any time. |
| **Privacy Policy URL** | Link to the brand's privacy policy page. Configured per brand (moved here from the main Configuration settings). |

Validation Rules:

| Rule | Behavior |
| --- | --- |
| Brand name duplicate | ✅ Allowed |
| Internal name duplicate | ❌ Not allowed (must be unique within a company) |
| Name equals internal name | ✅ Allowed |
| Maximum length | 50 characters |
| Minimum length | 1 character |
| Special characters | ✅ Allowed |
| Same names across different companies | ✅ Allowed |

### **Managing Brands**

#### **Permissions**

| Role | Capabilities |
| --- | --- |
| **Admin / Owner** | View brand list, add new brands, edit existing brands |
| **All other roles** | View the Brand column in the request table, filter requests by brand |

#### **Creating a New Brand**

1. Go to **DSR Setup**
2. Under the **Brands** section, click **+ New Brand**
3. In the dialog, fill in: 
     - **Name** (required)
     - **Internal Name** (optional)
     - **Creation type:** start with an empty brand, or duplicate the Privacy Center from an existing brand — a dropdown lets you select which brand's PC to copy
4. Click **Create**

![](https://docs.mineos.ai/hs-fs/hubfs/image-png-Mar-22-2026-09-10-19-9378-PM.png?width=435&height=647&name=image-png-Mar-22-2026-09-10-19-9378-PM.png)

After creation, complete your brand setup:

- **Customize the Privacy Center** — configure the form fields, languages, visual identity, and settings for this brand's Privacy Center
- **Set up a custom sender email** — navigate to the Custom Sender Address section at the bottom of the brand page to configure a branded email domain for outgoing communications
- **Customize email templates per Right** (optional) — in each Right's workflow, you can choose to set a different email template per brand, or keep a single template across all brands

Once created:

- The new brand appears at the bottom of the brand list, ordered by creation date
- A Brand ID is automatically generated
- A default logo placeholder is assigned — upload the real logo from the brand's page

#### **Editing a Brand**

All brand fields except the Brand ID can be edited at any time. Validation rules apply on every save.

 **Not available in this release.** Brand deletion and archiving are not supported. Brands cannot be deleted to prevent data loss and to ensure historical requests remain accessible.

### **Privacy Center per Brand**

Each brand has a **fully independent Privacy Center (PC)**. To configure a brand's Privacy Center, go to **DSR Setup → Privacy Center** — a dropdown next to the Privacy Center title lists all your brands, allowing you to switch between them and manage each one's configuration independently. Read more information about the Privacy Center and Multi-brand in [this article](https://developers.mineos.ai/docs/multibrand-and-the-privacy-center).

Each Privacy Center includes:

- A dedicated, unique URL
- Its own form and field configuration
- Independent language settings
- Separate custom code support
- Its own Privacy Policy URL

Copy reports are generated per brand Privacy Center URL.

#### **Languages**

The main language bank is defined company-wide in **DSR Setup \> Languages** and applies across all brands. Each brand can independently choose which languages from this bank to display in its Privacy Center.

The Languages section shows three states per language:

| State | Meaning |
| --- | --- |
| **Visible to customers** | Shown in all brands' Privacy Centers |
| **Not visible to customers** | Hidden in all brands' Privacy Centers |
| **Visible to some brands** | Shown in at least one brand, but not all (new) |

### **Email Templates per Brand**

MineOS has several types of email templates used throughout the DSR flow. The **Send reply to user** template is the one designed for personalized communication with the data subject — and because its content is most likely to differ between brands, it is the template that can be configured per brand. All other templates are more general communications and use a single version across all brands.

#### **The brandName variable**

*brandName* is a new variable available in all email templates. It resolves to the external brand name assigned to the ticket, ensuring that every outgoing email reflects the correct brand — regardless of whether you've configured separate templates per brand.

*brandName* replaces both *serviceName* and *companyName*, which previously appeared in template subject lines and body text. Both old variables still exist and will continue to resolve to the brand name, but they are no longer inserted into any template by default. If they remain in custom templates you have manually edited, they will continue to work.

#### **Template Types & Brand Customization**

| Template | Where to find it | Customizable per brand |
| --- | --- | --- |
| **Send reply to user** | DSR Setup → specific Right → specific workflow | ✅ Yes |
| **Send verification** | DSR Setup → specific Right → Rules & templates → Rules | ❌ No |
| **Send acknowledgement** | DSR Setup → specific Right → Rules & templates → Rules | ❌ No |
| **Rejection template** | DSR Setup → specific Right → Rules & templates → Rules → Default templates | ❌ No |
| **Send auto reply for closed requests** | DSR Setup → Rules | ❌ No |

For all templates where per-brand customization is not available, *brandName* will still resolve correctly based on the brand assigned to the ticket, so data subjects will always see the correct brand name.

#### **How to Set a Template per Brand (Send Reply to User)**

1. Go to **DSR Setup → specific Right → specific workflow**
2. Open the template selector and click **Set template per brand**
3. A side panel opens listing all brands — assign a template to each
4. Click **Done** to save

![Image 22-03-2026 at 23.50](https://docs.mineos.ai/hs-fs/hubfs/Image%2022-03-2026%20at%2023.50.jpeg?width=670&height=412&name=Image%2022-03-2026%20at%2023.50.jpeg)  
![Image 22-03-2026 at 23.50-1](https://docs.mineos.ai/hs-fs/hubfs/Image%2022-03-2026%20at%2023.50-1.jpeg?width=376&height=536&name=Image%2022-03-2026%20at%2023.50-1.jpeg)

 

**Note:** Closing the panel without clicking Done will show an unsaved changes dialog. Click **Discard** to close without saving, or **Cancel** to return to the panel.

When templates differ across brands, the workflow view changes: instead of a single template dropdown, only the panel open button is shown, with a **"Multiple templates selected"** indicator.

When a new brand is added to an account that already has per-brand templates configured, the new brand automatically inherits the template assigned to the default brand.

### **Custom Email Domain per Brand**

Each brand can be configured with its own custom email sender domain — the "From" address that data subjects see in all outgoing email communications sent from MineOS for that brand, including email templates and Privacy Center verification emails.

**Navigate to:** DSR Setup → Brand page → **Custom Sender Address** section (scroll to the bottom of the brand page)

![Image 23-03-2026 at 0.42 (1)](https://docs.mineos.ai/hs-fs/hubfs/Image%2023-03-2026%20at%200.42%20(1).jpeg?width=670&height=440&name=Image%2023-03-2026%20at%200.42%20(1).jpeg)

#### **Setup Steps**

1. Click **Edit Address**
2. Enter the full email address (e.g., `noreply@yourbrand.com`)
3. Click **Continue**
4. Copy the provided DNS records into your DNS manager
5. Click **Verify domain records** in MineOS
6. MineOS verifies the records via SendGrid: 
     - ✅ If all checks pass → custom domain becomes active for that brand
     - ❌ If checks fail → MineOS indicates which records did not pass

#### **Domain Reuse Rules**

| Scope | Rule |
| --- | --- |
| **Within a company** | A domain can be reused across multiple brands. Each brand can use a different full email address on the same domain (e.g., privacy@brand.com vs noreply@brand.com). If the domain is already verified, the verification step is skipped. |
| **Across companies** | A domain cannot be shared between different companies. |

#### **Removing a Custom Domain**

Removing a custom domain resets that brand's sender to the default no-reply@saymine.io address. Only after removal can a new custom domain be configured for that brand.

**Note:** Removing a domain that is shared with other brands only affects the brand it's removed from. The domain remains active for other brands. Removal must be done brand by brand.

### **Ticket Operations**

#### **Creating Requests Manually**

Brand selection is **required** when creating a request manually, and appears first in the form.

- The default brand is pre-selected
- If multiple brands exist, a dropdown appears to choose the brand
- Selecting a different brand loads that brand's Privacy Center form fields

#### **Importing Requests via CSV**

A `brandID` column is added in the import template. If left blank, the request is assigned to the default brand. You can copy the Brand ID from the brand's page in DSR Setup. 

 **Important:** Please update to the new CSV import template before importing. Importing a CSV without the brandID column will result in errors.

#### **Request Table**

The requests table includes a filterable **Brand** column, and there are now in the left-side Requests page menu pre-defined views for each brand.

#### **Individual Ticket Page**

Each ticket displays the brand it belongs to. The brand can be changed after creation.

When a brand is changed on a ticket:

- An entry is added to the ticket's **audit log**
- All other ticket fields remain unchanged, even if the new brand's Privacy Center has different form fields

### **API**

The Multi-Brand API is fully **backward compatible**. Click [here](https://developers.mineos.ai/reference/get_api-ticket-ticketid) to review the API docs in MineOS developers hub.

| Endpoint / Feature | Change |
| --- | --- |
| **Create Ticket** | New optional `brand-id` field. If omitted, the default brand is used automatically. |
| **Get Ticket** | Response now includes `brand-id`. Tickets created before Multi-Brand was enabled return the default brand-id. |
| **DSR Webhooks** | `Request created` and `Request closed` payloads now include `brand-id`. |
| **Custom Integrations** | `brand-id` added to the HTTP request payload. |
| **Prismatic Integrations** | `brand-id` added to the HTTP request payload. |
| **Create Brand via API** | Not supported — brands are created through the MineOS UI only. |

### **Settings Navigation Changes**

The Multi-Brand release includes a settings reorganization that applies to **all accounts**, regardless of whether Multi-Brand is enabled.

#### **Main Settings**

All DSR-related settings have been moved out of Main Settings into DSR Setup. As part of this, a new **General** page has been added to Main Settings, consolidating company-level information in one place: company name, company ID, and company logo (previously under Branding).

#### **DSR Setup**

The DSR Setup menu has been reorganized and now includes:

- **Privacy Rights**
- **Templates**
- **Languages**
- **Rules** *(now also includes PII Redaction)*
- **Brands** *(new — lists all brands, with + New brand option)*
- **Channels** *(new title)* — with dedicated sub-pages for: 
    - Privacy Center
    - Email forwarding
    - Toll-free phone number

### **Behavior Without Multi-Brand Enabled**

All accounts — including those without Multi-Brand — now operate with the Brand concept. For accounts without the Multi-Brand feature active:

- Only one brand exists (the default brand), initialized with the company name
- There is no option to add new brands
- A banner in DSR Setup informs the customer that Multi-Brand is available as an upgrade
- The brand Name, Internal name and logo can still be edited by Admins and Owners

### **Need Help?**

If you have questions about managing privacy rights, contact your system administrator or reach out to your MineOS CSM.

- [Data Inventory](https://docs.mineos.ai/knowledge/data-inventory#main-content)

    - [Systems](https://docs.mineos.ai/knowledge/data-inventory#systems)
    - [Data types](https://docs.mineos.ai/knowledge/data-inventory#data-types)
    - [Activities](https://docs.mineos.ai/knowledge/data-inventory#activities)
- [Compliance Operations](https://docs.mineos.ai/knowledge/compliance-operations#main-content)

    - [Compliance reports](https://docs.mineos.ai/knowledge/compliance-operations#compliance-reports)
    - [Policies & alerts](https://docs.mineos.ai/knowledge/compliance-operations#policies-alerts)
    - [Risk assessments](https://docs.mineos.ai/knowledge/compliance-operations#risk-assessments)
- [DSR Handling](https://docs.mineos.ai/knowledge/dsr-handling#main-content)

    - [Setting Up Channels](https://docs.mineos.ai/knowledge/dsr-handling#setting-up-channels)
    - [Configuring Responses](https://docs.mineos.ai/knowledge/dsr-handling#configuring-responses)
    - [Processing Requests](https://docs.mineos.ai/knowledge/dsr-handling#processing-requests)
    - [Audit & Reporting](https://docs.mineos.ai/knowledge/dsr-handling#audit-reporting)
    - [Setting Up Rights & Workflows](https://docs.mineos.ai/knowledge/dsr-handling#setting-up-rights-workflows)
- [Integrations](https://docs.mineos.ai/knowledge/integrations#main-content)

    - [General information](https://docs.mineos.ai/knowledge/integrations#general-information)
- [Settings & Security](https://docs.mineos.ai/knowledge/settings-security#main-content)

    - [Security](https://docs.mineos.ai/knowledge/settings-security#security)
    - [Your Account](https://docs.mineos.ai/knowledge/settings-security#your-account)
- [Developers Documentation](https://docs.mineos.ai/knowledge/developers-documentation#main-content)

    - [Portal for developers](https://docs.mineos.ai/knowledge/developers-documentation#portal-for-developers)
    - [Webhook](https://docs.mineos.ai/knowledge/developers-documentation#webhook)
    - [Other](https://docs.mineos.ai/knowledge/developers-documentation#other)
- [Release Notes](https://docs.mineos.ai/knowledge/release-notes)
- [Consent Management](https://docs.mineos.ai/knowledge/consent-management)

[![Frame 1948756858](https://docs.mineos.ai/hs-fs/hubfs/Frame%201948756858.png?width=62&height=40&name=Frame%201948756858.png "Frame 1948756858")](https://mineos.ai/)

Copyright © 2026, "MineOS" (Saymine Technologies Inc)