About full end-user separation (closed EAP)

<body>
<p id="docs-hc-snippet" style="display: none;">Full end-user separation isolates end-user data by brand. It's designed for companies who need stronger separation between departments, regions, or business units that share one account but should not share customer records.</p>
<div class="article-banners">
<div id="docs-wmp-link">
<a href="https://support.zendesk.com/hc/en-us/articles/5411234991258-plan" rel="noopener" target="_blank">What's my plan?</a>
</div>

<div class="article-banner" id="suite_ee">
<table>
<tbody>
<tr>
<td>
<strong>All Suites</strong>
</td>
<td>Enterprise or Enterprise Plus</td>
</tr>
</tbody>
</table>
</div>

<div class="article-banner" id="support_e">
<table>
<tbody>
<tr>
<td>
<strong>Support</strong>
</td>
<td>Enterprise</td>
</tr>
</tbody>
</table>
</div>

</div>
<div id="docs-ai-summary">
<p id="docs-ai-summary-toggle">Summary: <span id="up-triangle">◀</span><span id="down-triangle">▼</span></p>
<p id="docs-ai-summary-content">Full end-user separation isolates customer data by brand, creating separate user records, tickets, and histories for each brand. This supports privacy, regulatory compliance, and limits agent access to relevant brands. It suits companies needing strict data separation between departments or regions but has limitations like unsupported channels and no ticket brand changes. Testing workflows before production use is recommended.</p>
</div>

<div class="body">

<div class="note attention" id="zug_full_end_user_separation__note_mzg_jzw_zjc">
<span class="attentiontitle"></span> Full end-user separation is currently in a
closed Early Access Program (EAP). You can <a class="xref" href="https://forms.gle/YbiQeoTGpf2nZBCY9" target="_blank">sign up
for the EAP here</a>.</div>
<p class="p">Full end-user separation isolates end-user data by brand. It's designed for companies who
need stronger separation between departments, regions, or business units that share one
account but should not share customer records.</p>
<p class="p">With full end-user separation, each separated brand has its own end-user directory. The
same person can have a different user record in each separated brand, with separate
tickets, user fields, and history. This helps companies support stricter privacy,
regulatory, and operational requirements.</p>
<div class="p">This article covers the following topics:<ul class="ul" id="zug_full_end_user_separation__ul_qjw_mpw_zjc">
<li class="li"><a class="xref" href="#topic_qtv_vpw_zjc">Understanding full end-user separation</a></li>
<li class="li"><a class="xref" href="#topic_cf5_jqw_zjc">Reviewing how separated brands work</a></li>
<li class="li"><a class="xref" href="#topic_zhh_sqw_zjc">Considering EAP limitations and eligibility</a></li>
<li class="li"><a class="xref" href="#topic_jtv_zsw_zjc">Deciding whether to participate in the EAP</a></li>
<li class="li"><a class="xref" href="#topic_bw2_mtw_zjc">Getting started with the EAP</a></li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title2" class="topic nested1" id="topic_qtv_vpw_zjc">
<h2 class="title topictitle2" id="ariaid-title2">Understanding full end-user separation</h2>
<div class="body">
<p class="p">Full end-user separation is part of the <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/7584022494874" target="_blank">department spaces</a> feature. It fully isolates end-user
data between brands that are configured as separated brands.</p>
<p class="p">In a standard multi-brand account, end-user records can be shared across brands. With
full end-user separation, a separated brand keeps its own directory of end users. If
the same person interacts with multiple separated brands, Zendesk creates a separate
user record for each brand instead of sharing one record across the account.</p>
<p class="p">This model helps solve common problems for larger companies, including:</p>
<ul class="ul" id="topic_qtv_vpw_zjc__ul_klc_gqw_zjc">
<li class="li">Preventing end-user data from being visible across departments when it should be
isolated</li>
<li class="li">Supporting different customer data sets for different brands</li>
<li class="li">Meeting geographic, regulatory, or internal policy requirements for data
separation</li>
<li class="li">Limiting agent access to only the end-user profiles associated with the brands
they work in</li>
</ul>
<p class="p">For example, one customer might contact two brands in the same account using the same
email address. With full end-user separation, that person can exist as two separate
end-user records, one in each separated brand, without identity conflicts.</p>
</div>
</div>
<div aria-labelledby="ariaid-title3" class="topic nested1" id="topic_cf5_jqw_zjc">
<h2 class="title topictitle2" id="ariaid-title3">Reviewing how separated brands work</h2>
<div class="body">
<p class="p">A separated brand is a brand that is created with full end-user separation enabled.
When a brand is separated, end-user data created in that brand is isolated from
other brands. Brands that are not separated continue to work as they do today and
continue sharing end-user data with each other.</p>
<p class="p">Full end-user separation includes the following behavior:</p>
<ul class="ul" id="topic_cf5_jqw_zjc__ul_ywd_mqw_zjc">
<li class="li">End-users created in a separated brand are visible only in that brand.</li>
<li class="li">The same person can have separate user profiles in different brands.</li>
<li class="li">Each profile has its own tickets, fields, and history.</li>
<li class="li">Email addresses, phone numbers, and external IDs can be reused across separated
brands.</li>
<li class="li">Identity matching happens within the brand, not across the entire account.</li>
<li class="li">Help center authentication is scoped to the brand, so end users sign in
separately for different separated brands.</li>
<li class="li">End users in separated brands can only be accessed by agents assigned to those
brands.</li>
</ul>
<p class="p">Separated end users are also limited to interactions within their own brand. An end
user in a separated brand can only be a requester, CC, or participant on tickets in
that same brand.</p>
<p class="p">Organizations are not separated by brand. Organizations remain outside of brands, and
both brand-scoped and global users can belong to any organization.</p>
</div>
</div>
<div aria-labelledby="ariaid-title4" class="topic nested1" id="topic_zhh_sqw_zjc">
<h2 class="title topictitle2" id="ariaid-title4">Considering EAP limitations and eligibility</h2>
<div class="body">
<p class="p">This EAP is a first release and has important limitations. Because this is a closed
EAP, participation is also subject to Zendesk eligibility criteria.</p>
</div>
<div aria-labelledby="ariaid-title5" class="topic nested2" id="topic_nzb_vqw_zjc">
<h3 class="title topictitle3" id="ariaid-title5">Brand requirements</h3>
<div class="body">
<div class="p">
<ul class="ul" id="topic_nzb_vqw_zjc__ul_nlg_wqw_zjc">
<li class="li">Full separation can be enabled only on new brands.</li>
<li class="li">Existing brands are not supported in this release.</li>
<li class="li">After a brand is created as separated, you cannot turn separation
off.</li>
<li class="li">After a user is assigned to a department or separated brand, that user
cannot be reassigned to another department or brand.</li>
</ul>
</div>
<p class="p">Zendesk plans to support existing brands in a later release.</p>
</div>
</div>
<div aria-labelledby="ariaid-title6" class="topic nested2" id="topic_lw4_1rw_zjc">
<h3 class="title topictitle3" id="ariaid-title6">Unsupported channels</h3>
<div class="body">
<p class="p">The following channels aren't supported in this EAP:</p>
<ul class="ul" id="topic_lw4_1rw_zjc__ul_hg2_2sw_zjc">
<li class="li">Voice</li>
<li class="li">Contact Center</li>
<li class="li">Talk Partner Edition</li>
<li class="li">X Corp public posts</li>
<li class="li">Public Facebook messaging</li>
<li class="li">Channels Framework API integrations</li>
</ul>
<p class="p">The following related channels are supported:</p>
<ul class="ul" id="topic_lw4_1rw_zjc__ul_m5z_3sw_zjc">
<li class="li">X Corp direct messages using messaging</li>
<li class="li">Facebook Messenger using messaging</li>
</ul>
</div>
</div>
<div aria-labelledby="ariaid-title7" class="topic nested2" id="topic_z3n_ksw_zjc">
<h3 class="title topictitle3" id="ariaid-title7">Ticketing limitations</h3>
<div class="body">
<div class="p">
<ul class="ul" id="topic_z3n_ksw_zjc__ul_brr_lsw_zjc">
<li class="li">You can't change the brand on a ticket that belongs to a separated
brand.</li>
<li class="li">You can't move a ticket into a separated brand after the ticket is
created.</li>
<li class="li">Triggers or automations that try to change the brand on a ticket in a
separated brand will not make the change.</li>
<li class="li">You can't merge tickets across brands if either brand is separated.</li>
<li class="li">Tickets can be merged only within the same brand.</li>
<li class="li">Agents can't add CCs or followers who don't have access to the ticket's
brand.</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title8" class="topic nested2" id="topic_h21_ssw_zjc">
<h3 class="title topictitle3" id="ariaid-title8">User and agent limitations</h3>
<div class="body">
<ul class="ul" id="topic_h21_ssw_zjc__ul_qhw_ssw_zjc">
<li class="li">End users in a separated brand can be merged only with other end users in
that same brand.</li>
<li class="li">Agents who have interacted with more than one brand can't be downgraded to a
customer.</li>
<li class="li">Customers who have interacted with more than one brand can't be upgraded to
an agent.</li>
</ul>
</div>
</div>
</div>
<div aria-labelledby="ariaid-title9" class="topic nested1" id="topic_jtv_zsw_zjc">
<h2 class="title topictitle2" id="ariaid-title9">Deciding whether to participate in the EAP</h2>
<div class="body">
<p class="p">Full end-user separation may be a good fit if your company needs to isolate customer
data between brands while still managing those brands in one account.</p>
<p class="p">You may want to participate if you need to:</p>
<ul class="ul" id="topic_jtv_zsw_zjc__ul_t4y_ctw_zjc">
<li class="li" dir="ltr">Keep customer records separate between departments or business
units.</li>
<li class="li" dir="ltr">Support different user profiles for the same person in different
brands.</li>
<li class="li" dir="ltr">Reuse the same email address, phone number, or external ID in
different brands.</li>
<li class="li" dir="ltr">Restrict agent visibility so agents see only the end users in the
brands they can access.</li>
<li class="li" dir="ltr">Better align Zendesk with your internal data model.</li>
<li class="li" dir="ltr">Support privacy or regulatory requirements that require stronger
separation of customer data.</li>
</ul>
<p class="p" dir="ltr">This EAP may not be a good fit if you need to:</p>
<ul class="ul" id="topic_jtv_zsw_zjc__ul_ok3_3tw_zjc">
<li class="li" dir="ltr">Apply separation to existing brands immediately.</li>
<li class="li" dir="ltr">Use unsupported channels such as Voice or Contact Center.</li>
<li class="li" dir="ltr">Move tickets between brands after they are created.</li>
<li class="li" dir="ltr">Maintain cross-brand workflows that depend on shared end-user
records.</li>
</ul>
<p class="p">If you are evaluating the EAP, review your current brand structure, channels,
automations, and ticket routing rules carefully. In particular, check whether any
existing workflows depend on changing ticket brands or sharing end-user identities
across brands.</p>
</div>
</div>
<div aria-labelledby="ariaid-title10" class="topic nested1" id="topic_bw2_mtw_zjc">
<h2 class="title topictitle2" id="ariaid-title10">Getting started with the EAP</h2>
<div class="body">
<p class="p">If your company is interested in the EAP, complete the <a class="xref" href="https://forms.gle/YbiQeoTGpf2nZBCY9" target="_blank">sign-up form</a>.</p>
<p class="p" dir="ltr">If you're approved for the EAP, the basic setup flow is:</p>
<ol class="ol" id="topic_bw2_mtw_zjc__ol_j5t_ttw_zjc">
<li class="li" dir="ltr">Request to participate in the EAP, then wait for confirmation that the
EAP has been enabled on your account.</li>
<li class="li" dir="ltr">In Admin Center, <a class="xref" href="https://support.zendesk.com/hc/en-us/articles/4408829476378#topic_bp3_gby_wp" target="_blank">create a brand</a> with full separation
enabled.</li>
<li class="li" dir="ltr">
<a class="xref" href="https://support.zendesk.com/hc/en-us/articles/7584022494874#topic_p4k_grx_xbc" target="_blank">Add team members to the brand</a> so they
can access its tickets and end users.</li>
<li class="li" dir="ltr">Test your workflows in a sandbox before using the feature in
production.</li>
</ol>
<p class="p" dir="ltr">Testing is strongly recommended because separation affects identity
matching, authentication, ticket participation, and brand-based visibility.</p>
</div>
</div>
<script id="docs-schema-markup" type="application/ld+json">{
"@context": "https://schema.org",
"@type": "TechArticle",
"@id": "https://support.zendesk.com/hc/en-us/articles/11046915478938-About-full-end-user-separation-closed-EAP",
"url": "https://support.zendesk.com/hc/en-us/articles/11046915478938-About-full-end-user-separation-closed-EAP",
"headline": "About full end-user separation (closed EAP)",
"description": "You can isolate end-user data by brand within a single account to meet privacy, regulatory, and operational requirements by enabling full end-user separation for new brands in a closed Early Access Program.",
"articleSection": "Product help",
"datePublished": "2026-07-23T17:58:33+00:00",
"dateModified": "2026-07-23T18:08:11.381796+00:00",
"inLanguage": "en-US",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://support.zendesk.com/hc/en-us/articles/11046915478938-About-full-end-user-separation-closed-EAP"
},
"author": {
"@type": "Organization",
"name": "Zendesk",
"url": "https://www.zendesk.com"
},
"publisher": {
"@type": "Organization",
"name": "Zendesk"
},
"isPartOf": {
"@type": "WebSite",
"name": "Zendesk Help",
"url": "https://support.zendesk.com/hc/en-us"
},
"about": {
"@type": "SoftwareApplication",
"name": "Zendesk"
}
}</script><script id="ai-summary-script">
//<![CDATA[
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//]]>
</script>
</body>