<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Domain Separation - Need to Enable Email Functionality for Domain-Specific Users Without Admin Acces in Community Central forum</title>
    <link>https://www.servicenow.com/community/community-central-forum/domain-separation-need-to-enable-email-functionality-for-domain/m-p/3236998#M2751</link>
    <description>&lt;P class=""&gt;Hi Community,&lt;/P&gt;&lt;P class=""&gt;I’ve implemented domain separation on my demo instance and created multiple domains. I'm now working on setting up Incident Management within a specific domain, and I’ve categorized the service into tier levels: Bronze, Silver, Gold, and Platinum.&lt;/P&gt;&lt;P class=""&gt;For the Bronze tier, I need to allow users to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;Create incidents via email&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;Receive incident status updates via email&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;However, I’m running into a problem:&lt;BR /&gt;In ServiceNow, it appears that only admin users can access and configure email functionality, such as email receiving and notifications. Due to domain separation, I cannot grant admin roles to users within a domain because it would give them visibility and access to other domains, which violates the isolation requirement.&lt;/P&gt;&lt;P class=""&gt;My question is:&lt;BR /&gt;What is the best practice or recommended way to enable email-based incident creation and status updates for users within a specific domain, without assigning them admin-level roles that cross domain boundaries?&lt;/P&gt;&lt;P class=""&gt;Any guidance or workarounds would be greatly appreciated!&lt;/P&gt;&lt;P class=""&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Mon, 14 Apr 2025 12:15:03 GMT</pubDate>
    <dc:creator>muslimaltaf</dc:creator>
    <dc:date>2025-04-14T12:15:03Z</dc:date>
    <item>
      <title>Domain Separation - Need to Enable Email Functionality for Domain-Specific Users Without Admin Acces</title>
      <link>https://www.servicenow.com/community/community-central-forum/domain-separation-need-to-enable-email-functionality-for-domain/m-p/3236998#M2751</link>
      <description>&lt;P class=""&gt;Hi Community,&lt;/P&gt;&lt;P class=""&gt;I’ve implemented domain separation on my demo instance and created multiple domains. I'm now working on setting up Incident Management within a specific domain, and I’ve categorized the service into tier levels: Bronze, Silver, Gold, and Platinum.&lt;/P&gt;&lt;P class=""&gt;For the Bronze tier, I need to allow users to:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;Create incidents via email&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;Receive incident status updates via email&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;However, I’m running into a problem:&lt;BR /&gt;In ServiceNow, it appears that only admin users can access and configure email functionality, such as email receiving and notifications. Due to domain separation, I cannot grant admin roles to users within a domain because it would give them visibility and access to other domains, which violates the isolation requirement.&lt;/P&gt;&lt;P class=""&gt;My question is:&lt;BR /&gt;What is the best practice or recommended way to enable email-based incident creation and status updates for users within a specific domain, without assigning them admin-level roles that cross domain boundaries?&lt;/P&gt;&lt;P class=""&gt;Any guidance or workarounds would be greatly appreciated!&lt;/P&gt;&lt;P class=""&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Apr 2025 12:15:03 GMT</pubDate>
      <guid>https://www.servicenow.com/community/community-central-forum/domain-separation-need-to-enable-email-functionality-for-domain/m-p/3236998#M2751</guid>
      <dc:creator>muslimaltaf</dc:creator>
      <dc:date>2025-04-14T12:15:03Z</dc:date>
    </item>
  </channel>
</rss>

