UPDATE

administration/about-permissions/index.html

@@ -269,7 +269,7 @@ <h2 id="how-it-works">How it works</h2>
 <p class="tip"><i class="fa fa-info-circle"></i>Client-side profiles are separate from server-side profiles, but a single permission group can grant access to both.</p>
 <p>An <a href="/administration/admin-roles/"><em>admin role</em></a> grants access to features and settings that affect the entire account. A user with an admin role receives those permissions regardless of their permission group membership, which makes it easier for you to delegate management of your account to specific users. Users without admin roles receive only the access to the account they obtain through their membership in permission groups.</p>
 <h3 id="new-user-activation">New user activation</h3>
-<p>When you invite users to your account, they receive an email to active their account. After a user activates their account, add them to a permission group with the appropriate profile and product feature access. You can add a user to multiple permission groups to grant the user greater access to the profiles, such as publishing rights.</p>
+<p>When you invite users to your account, they receive an email to activate their account. After a user activates their account, add them to a permission group with the appropriate profile and product feature access. You can add a user to multiple permission groups to grant the user greater access to the profiles, such as publishing rights.</p>
 <h3 id="dynamic-user-interface">Dynamic user interface</h3>
 <p>The interface changes based on the user&rsquo;s permissions:</p>
 <ul>
@@ -291,7 +291,7 @@ <h2 id="setup-plan">Setup plan</h2>
 <p>As you progress through your plan, you may identify the need for more profiles and permission groups to access those profiles.</p>
 <p>For help with migrating your existing settings to the platform permissions system, see <a href="/administration/permissions-system-migration-guide/">Permissions System Migration Guide</a>.</p>
 <h3 id="publish-permissions">Publish permissions</h3>
-<p>Because server-side publishing requires a user to see everything in an account, a user in a permission group with server-side publish permissions automatically has full access to all server-side products and features in addition to any other rights they receive from that or other permission groups.</p>
+<p>Because server-side publishing requires a user to see everything in an account, a user in a permission group with server-side publish permissions automatically receives full access to all server-side products and features in addition to any other rights they receive from that or other permission groups.</p>
 <p>For example, if User X is a member of Permission Group Y and Permission Group Y has server-side publishing access, User X will have full access on every server-side product and feature.</p>
 <h2 id="access-the-manage-permissions-screen">Access the Manage Permissions screen</h2>
 <p class="tip"><i class="fa fa-info-circle"></i>Only users with the account admin or user admin roles can access this screen. For more information, see <a href="/administration/admin-roles/">Admin roles</a>.</p>
@@ -347,7 +347,7 @@ <h2 id="access-the-manage-permissions-screen">Access the Manage Permissions scre
 
         </div>
         <div class="bt-l b--moon-gray pt3 f6">
-          <p>This page was last updated:  October 30, 2023 
+          <p>This page was last updated:  November 6, 2023 
             &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
           </p>
         </div>

administration/permission-groups/index.html

@@ -26,7 +26,7 @@
 <script>
 var utag_data = {
     site_section  : "administration",
-    reading_time  : "6",
+    reading_time  : "7",
     site_language : "en",
     tealium_event : "page_view"
 }
@@ -315,6 +315,7 @@ <h3 id="publishing-permissions">Publishing permissions</h3>
 <li>On the server-side, set publishing rights on the <strong>Group Permissions</strong> tab of the permission group.</li>
 </ul>
 <p>Permission groups have publishing rights on the profiles to which you give them access.</p>
+<p>Remember, a permission group can also be granted publishing rights for server-side profiles. Users who are members of a permission group with server-side publishing rights have full access to all server-side products and features in addition to any other permissions they receive from that or other permission groups.</p>
 <!-- #### Publishing changes to features in multiple products
 
 If you disable a product for a user, but the user has server-side publish permission and access to another product that shares features with the first product, the user can still publish changes to those shared features. For example, EventStream and AudienceStream share some features, such as rules and labels.
@@ -463,7 +464,7 @@ <h3 id="manage-user-permission-groups">Manage user permission groups</h3>
 
         </div>
         <div class="bt-l b--moon-gray pt3 f6">
-          <p>This page was last updated:  October 30, 2023 
+          <p>This page was last updated:  November 6, 2023 
             &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
           </p>
         </div>

administration/permissions-system-migration-guide/migration-about/index.html

@@ -291,7 +291,7 @@ <h2 id="terminology">Terminology</h2>
 <h2 id="tealiums-project-rollout-plan">Tealium&rsquo;s project rollout plan</h2>
 <p>We plan to roll out platform permissions in the following steps:</p>
 <ol>
-<li>All new customers after September 2023 use platform permissions to manage their Tealium account.</li>
+<li>All new customers after November 2023 use platform permissions to manage their Tealium account.</li>
 <li>Existing customers are migrated to EEA platform permissions without Permissions Enforcement enabled, so they can continue to use legacy permissions until they are ready to migrate.</li>
 <li>Tealium assists existing customers with setting up platform permissions for their accounts.</li>
 <li>Customers enable Permissions Enforcement to change from legacy to platform permissions.
@@ -357,7 +357,7 @@ <h2 id="benefits-of-migration">Benefits of migration</h2>
 
         </div>
         <div class="bt-l b--moon-gray pt3 f6">
-          <p>This page was last updated:  October 13, 2023 
+          <p>This page was last updated:  November 6, 2023 
             &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
           </p>
         </div>

administration/permissions-system-migration-guide/plan/index.html

@@ -666,7 +666,7 @@ <h2 id="sort-the-users-into-groups">Sort the users into groups</h2>
 <ul>
 <li>The profiles users in the group needs to access.</li>
 <li>The level of access group members need on each profile.</li>
-<li>Whether group members should have publishing rights for client-side and server-side profiles.</li>
+<li>Whether group members should have publishing rights for client-side and server-side profiles. Because users with server-side publishing rights also have full access to all server-side products and features, you should be careful which groups are granted those rights.</li>
 <li>The products and product features each group should be able to access.</li>
 <li>The level of access each group should have on each product feature.</li>
 <li>Whether users should have access to PII data.</li>
@@ -755,7 +755,7 @@ <h2 id="add-admin-roles">Add admin roles</h2>
 
         </div>
         <div class="bt-l b--moon-gray pt3 f6">
-          <p>This page was last updated:  October 30, 2023 
+          <p>This page was last updated:  November 6, 2023 
             &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
           </p>
         </div>