Surfaces, roles and current terminology

Permissions, settings and activation

• Grant the exact Pages, Additional Pages, Testimonials, Tags, Comments, Content Delete Requests, Regions, and Instructor Finder permissions needed by each staff role.
• Comment permissions can differ by content family and action; list access does not imply reply, edit, publish, report review, or delete access.
• Additional Pages have separate permissions for error settings, Contact Us, and Top Navbar.
• Regions and Instructor Finder currently display an inactive feature status in this source build. Do not document their menu entries as usable management workflows.

Core workflows

Moderate unified comments

1. Open CRM ? Comments and select the relevant family: Courses, Bundles, Blog, Products, Events, or Jobs.
2. Filter by search, date, status, and the applicable content item.
3. Review the comment and any abuse-report context before replying, editing, publishing, or deleting.
4. Confirm totals and the public content page reflect the final moderation state.

Maintain system and additional pages

1. Use Content ? Pages for general CMS pages and preserve stable slugs when editing published content.
2. Use Additional Pages ? Error Settings to maintain 404, 500, 419, and 403 content, including locale-specific values when translation is enabled.
3. Use Contact Us for phones, emails, address, map position, and additional information.
4. Use Top Navbar for localized link title, destination, and order; verify the link on the public header after saving.

Maintain supporting content

1. Create or update Testimonials with user identity, rating, content, and publication status.
2. Create, edit, or delete Tags only after checking their current content usage.
3. Review Content Delete Requests by content type, owner, customer/sales context, reason, date, and status before approving or rejecting.
4. For Regions or Instructor Finder, stop at the inactive status and use Activations or SOQ support rather than attempting a workflow that is not present.

Result states

• Success: The content saves, moderation status is correct, public output matches the selected locale/order, and deletion decisions update the request queue.
• Pending: A comment awaits moderation, a deletion request awaits review, or content remains draft/unpublished.
• Denied: The staff role lacks the specific content/action permission, or the requested surface is inactive.
• Error: Validation, linked-content usage, locale data, or save/delete failure prevents completion; preserve the existing public content until corrected.

Operational notes

• A menu permission or route can expose a location without proving the feature UI is active. This guide classifies the rendered source view, not the label alone.
• Use the configured Admin URL throughout; /admin is only a default example.

Related guides

• Custom Pages
• Blog
• Contacts
• Reports
• Admin Communications Operations
• Feature Pack Bundle