This release brings a major evolution to document governance: administrators can now apply corrective actions directly on documents and delegate them to document owners through campaigns. Campaign analytics also get a significant round of improvements, a new test preview, more reliable notification figures, filtering options, and a reworked notified users list.

This release is scheduled for Tuesday, August 25th, 2026

Document Campaigns & Corrective Actions  

Until now, the only action available on a document was revoking a sharing link, and any document-level action had to be handled manually by the admin, there was no way to delegate it to the person accountable for the document.

Administrators can now apply corrective actions on documents directly, or request them from the document's resolved owner through a campaign, reusing the same campaign mechanism already available for Teams and SharePoint sites.

The following corrective actions are available, both for direct use by the admin and as a campaign request:

• Revoke a sharing link — already available today, unchanged.
• Mark as verified / obsolete — a Powell Governance-level status flag used for reporting and as a campaign ask. This status is not written back to SharePoint.
• Edit the document title — correct or update the title directly, with the change written back to SharePoint/Microsoft 365.

Test Campaign: Preview and Export Scope

Testing a campaign previously launched it directly, with no visibility into its scope beforehand, making it impossible to validate the configuration before notifications were sent.

Clicking Test campaign now opens a preview modal showing the scope of the test before it is triggered:
 

• The number of users who will be notified and the number of workspaces in scope are displayed.
• This data reflects the campaign's current configuration, including any audience filters applied.
• The data can be exported (CSV) for further analysis outside the platform.
• From the modal, the administrator can confirm and proceed with the test, or go back and adjust the campaign configuration

Notified Users List

The "Top User" table in campaign analytics has been reworked into a reliable list of notified users, based on a defined scoring logic (workspaces owned and actions taken) rather than the previous, unclear implementation. This gives administrators an accurate view of who was notified and how, along with the number of workspaces each user is responsible for.

 

Filterable Campaign Analytics

The Past action(s) table in campaign analytics already supported filtering by name and by date. It can now also be filtered by:

• Action type (e.g. Archive, Add owners, and other existing action types)

• Made by (the user who performed the action)

Existing filters (name, date) and the CSV export remain unchanged.

Smaller updates :

User names property in reports: a new "User names" column, using a people picker, is now available in the report builder and in report tables, for owners, members, visitors, and guests on sites and teams (max 2 users shown per cell, not filterable). 

Campaign analytics reflect security group filters: when a campaign's audience is restricted by a security group, analytics figures now reflect that filtered audience instead of the campaign's full unfiltered scope. 

Reworked notification counter: the counter now shows the number of users notified, with open/response status broken down per channel (Teams / Mail / not opened)

This release strengthens document governance with a full set of delegable corrective actions, and gives administrators much clearer, more trustworthy visibility into how their campaigns perform. As always, feel free to reach out to our support team with any questions.