# Page List

### Overview

The **Page List** provides a centralized view of all pages across the domain, allowing administrators to manage content at scale from a single location.

<figure><img src="/files/NoMPE50JPEzynYcMOivv" alt=""><figcaption></figcaption></figure>

Accessible via **Admin Portal → Domain → Pages → Page List**, this view includes both company and team pages, making it easy to monitor, organize, and take action on content across the network.

***

The **Page List** displays all pages in a structured table with key information and associated metadata. This layout allows administrators to quickly understand the state and ownership of content across the organization.&#x20;

* **Title** – Name of the page
* **Status** – Draft, Published, Archived, Pending Approval, or Declined
* **Author** – Page creator
* **Team** – Associated team or company context
* **Last Modified** – Most recent update date
* **Total Views** – Page engagement metric
* **Governance** – Indicates if governance rules are applied
* **Hashtags and Languages** – Additional metadata (optional columns)

By default, pages are sorted by **Last Modified (newest first)**.

***

### Search, Sort, and Filter

To help administrators efficiently locate specific pages, the **Page List** includes search, sorting, and filtering capabilities. Admins can search by page title, sort by any column, and apply filters such as author, status, team, and governance. Multiple filters can be applied simultaneously, with results updating in real time.

***

### Page Status Visibility

The **Page List** provides full visibility into the page lifecycle by including pages in all states. This includes drafts, pages pending approval, declined pages, published pages, and archived content. By surfacing all statuses in one place, administrators can easily track progress, identify bottlenecks, and manage both active and in-progress content.

***

### Row-Level Actions

Each entry in the list includes a context menu that provides access to actions relevant to that specific page. Depending on the page’s status, administrators can edit the page, view version history, access page insights, save it as a template, manage governance settings, duplicate it, or take actions such as archiving or deleting.

{% hint style="warning" %}
Home pages and system pages **cannot** be archived or deleted
{% endhint %}

#### Edit Page

Editing pages is subject to certain constraints based on page type, layout, permissions, and workflow configuration.

Some pages have restricted editing capabilities. **Home pages and system-generated pages** cannot be archived or deleted, and certain actions may be limited compared to regular pages.

Layout changes have specific limitations. Only pages built using modern templates can be converted to a 4-column layout, and once a page is published in this layout, it cannot be reverted to a previous format.

If approval workflows are configured, changes made during editing may not go live immediately. Instead, the page enters a **Pending Approval** state, and only one approval request can be active per page at a time.

Editing permissions vary by role. Actions such as updating governance settings or moving a page require appropriate admin privileges, and in some cases, permissions across both source and destination teams.

When multiple users attempt to edit the same page, an edit lock is applied to prevent conflicts. Another user can take over editing after a period of inactivity, but doing so may override any unsaved changes from the original editor.

Draft handling is automatic. Changes made during editing are saved as drafts unless explicitly discarded, and only published changes are reflected on the live page.

***

#### Version History

Page Version History allows administrators to view and manage previous versions of a page, providing visibility into how content has evolved over time. This helps ensure accountability, supports content recovery, and enables better tracking of updates made by different users.

Each time a page is published, a new version is created and stored automatically. The version history includes details such as the user who made the changes and the date and time of publication, allowing admins to understand when updates occurred and who was responsible.

<figure><img src="/files/eRiALFhv6iXXE6Wb0FtR" alt="" width="563"><figcaption></figcaption></figure>

From the Page List or page actions menu, administrators can access the version history for a specific page. This view provides a chronological record of published versions, making it easy to review past content and compare changes as needed.

Version history is especially useful in collaborative environments where multiple users contribute to page updates. It provides a reliable audit trail and ensures that previous versions of content can be referenced if needed.

{% hint style="warning" %}
Only published versions are tracked in version history. Draft changes remain separate and **are not** included until they are published.
{% endhint %}

***

#### Page Insights

Page Insights provides administrators with visibility into how pages are performing, helping them understand engagement and optimize content over time.

Insights can be accessed from the page actions menu and include key metrics such as total views and user interactions. These metrics help administrators evaluate which pages are being accessed most frequently and identify content that may need updates or improved visibility.

<figure><img src="/files/aQKAFnla9xqsy0KLGVdE" alt="" width="563"><figcaption></figcaption></figure>

In addition to summary metrics, Page Insights includes trend data showing how views and interactions change over time. This allows admins to track engagement patterns, measure the impact of updates, and understand how users are interacting with page content.

Page Insights also includes Click Map engagement data, showing how users interact with links within a page. This helps identify which sections of a page are driving the most engagement and where users are clicking.

These insights support better content decisions by enabling administrators to monitor performance, identify gaps, and continuously improve the effectiveness of pages across the platform.

***

### Bulk Actions

Admins can select multiple pages (up to 100 at a time) and perform bulk operations, including:

* **Manage Governance** – Apply or remove governance rules
* **Set Hashtags** – Add or replace hashtags across selected pages
* **Copy Links** – Copy multiple page URLs at once
* **Archive** – Archive selected pages (home pages are skipped)
* **Delete** – Permanently delete selected pages (home pages are skipped)

These bulk actions are designed for large-scale content management.

***

### Audit Logging

To ensure accountability and traceability, all archive and delete actions performed from the Page List are recorded in the Audit Log. These records include details such as the page name, associated team, the action taken, the user who performed it, and the corresponding timestamp and IP address.

***

### Key Benefits

The **Page List** simplifies page administration by providing centralized visibility and control over all pages. It enables faster content management through bulk operations, improves governance oversight, and reduces the need to manage pages individually within each team.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guides.mangoapps.com/admin-guide/domain-settings/pages/page-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
