Release 2026 - April 24

• Powell Manager : Multi-partner access for PM users ❤️
•  Content Builder : Improved Button settings ❤️
• Breadcrumb :  Use theme color (body instead of header) ❤️
• Webpart editing panel :  Display Title
• Accessibility : Global improvements ❤️
• Accessibility : Add Lexend as an alternative accessibility font ❤️
• Email Notification : Microsoft Graph Sending Support & Email Security Settings ❤️
• Item Translation :  Per-list activation toggle ❤️

• Newsletter : Standardize button section height & image scaling ❤️
• Newsletter : Update "Recipients" field type ❤️

• Advanced Analytics : "Your Own Azure" configuration validation & connection test
• Advanced Analytics : Tracked data & filters redesign
• Advanced Analytics : Combine analytics for multilingual sites (MS Translation) ❤️

• Agents linked to Knowledge Bases
• Charts & Data Visualizations in Agent Answers

Previously, a Powell Manager user could only be associated with a single partner. Accessing multiple partners required creating separate PM accounts with different email addresses — one per partner. For Tenants such as  who manage several distinct projects with independent partners, this was impractical.

What's new :

Multi-partner association

• A single Manager account (email address) can now be associated with multiple partners.
• When Powell provisions a new Partner account, multiple partners can be selected in the user configuration panel (multi-select).
• All tenants linked to each selected partner remain accessible by default, consistent with existing behaviour.
• The tenant list is now grouped by partner to improve readability.

Partner-scoped user management

• When a Partner account creates or manages other users, a Partners section is displayed listing the available partners. At least one partner must be selected.
• Tenant selection is constrained to the partner(s) already selected — users cannot pick tenants from partners they have not been granted access to.

Content Builder buttons were previously limited to default styles, giving contributors no control over color, size, or positioning. This made it difficult to align buttons with brand guidelines or the visual design of a custom page.

What's new :

A new Display section has been added to the Button settings panel with the following controls:

• Background color — color picker (Hex/RGB or theme palette) to set the button fill.
• Text color — color picker to change the label color inside the button.
• Width — options to set the button width: fit to text, full width, or a custom pixel/percentage value.

Alignment — toggle to position the button within its container: Left, Center, or Right.

What's new

Screen reader message optimisation

• Several UI messages have been updated to improve their clarity and accuracy when read aloud by assistive technologies, as part of an ongoing effort to make the intranet more accessible to all users.

Contrast improvements

• The contrast management algorithm has been adjusted to improve text readability, particularly in components that use the primary theme color.

HTML semantics improvements

• Several tags and components have been updated to ensure a more consistent HTML structure, in line with accessibility best practices.

The accessibility font settings previously offered only OpenDyslexic. While effective for some users, a single option does not accommodate the range of reading preferences across users with dyslexia.

What's new

• Lexend — a sans-serif typeface with wider letterforms specifically designed to reduce reading friction — has been added as a second option in the accessibility font settings.

Users can now choose between OpenDyslexic and Lexend based on their personal preference.

Powell Manager now supports Microsoft Graph as an alternative email sending service for portal notifications, in addition to the existing SendGrid integration. Administrators can select their preferred sending method directly from the notification configuration panel and assign a dedicated sender account.

Alongside this, a new Email Security Settings panel is available, giving administrators fine-grained control over outbound email behavior:

 

• Maximum Recipients — cap the total number of recipients (To + Cc + Bcc) per email, or leave empty for no limit.
• Sanitize Tokens HTML — when enabled, HTML tags are stripped from token values before sending, returning plain text only.
• Enable AI Safety Analysis — when enabled, email content is analyzed by AI before sending to ensure it meets safety standards.
• Allowed Email Domains — restrict recipient addresses to specific domains; supports wildcards (e.g. *.company.com).
• Allowed Image Domains — only images hosted on listed domains will be permitted in email content (system images using cid: are always allowed).
• Allowed Link Domains — restrict hyperlinks in email content to approved domains.

These settings allow organizations with strict security and compliance requirements to align Powell notification emails with their internal policies.

Background

Item Translation was previously activated at the tenant level, automatically enabling the feature on all lists. Any sync operation — including adding a field — could trigger activation on lists where it was never intended. 

What's new

Per-list toggle

• Each SharePoint list now has its own Item Translation toggle in the Powell list settings panel.
• The toggle is OFF by default for all lists, including existing ones.
• Activating or deactivating the feature on one list has no effect on any other list.

Removal of tenant-level toggle

• The tenant-level Item Translation toggle has been removed from Powell Manager. No trace of the old control remains in the UI.

Migration of existing tenants

• For tenants where Item Translation was previously enabled at tenant level, all lists that had the feature active are automatically migrated to ON at list level during deployment.
• Lists that were not concerned remain OFF.

Sync behaviour

• Synchronizing a site, site template, or list — including adding a field — no longer modifies the Item Translation state of any list. The per-list configuration is preserved across all sync operations.

Powell native lists — Feature Dashboard

• For Powell-managed lists without a standard settings panel (e.g. header alerts), Item Translation activation is managed via the Feature Dashboard, consistent with how other features at this level are handled.

The newsletter button section previously used a flexible container that expanded to match the full height of any uploaded background image. Uploading a high-resolution or vertically tall image caused the section to grow disproportionately, breaking the visual layout of the newsletter.

• The button section now enforces a maximum height, regardless of the dimensions of the uploaded background image.
  
• Background images automatically scale and crop to fit the fixed container without stretching or distorting.

The Recipients field in the Newsletter editor previously used a plain text input, making it error-prone and difficult to validate entries against the directory.

 

What's new

• The Recipients field has been replaced with a people picker component.
  
  
• Contributors can now search and select recipients directly from the organization directory.

Background

Customers configuring their own Azure resources for Powell analytics ("Your Own Azure" mode) had no way to test or validate the configuration before saving. Errors — such as an incorrect connection string or an unreachable workspace — remained silent until the analytics pipeline failed.

What's new

Inline field validation

• Log Analytics Workspace ID and Client ID are validated against GUID format on blur.
• Application Insights Connection String is checked for the required InstrumentationKey= and IngestionEndpoint= tokens.
• Client Secret must not be empty.

• Format errors display an inline message below the field and apply an invalid visual state (red border, light red background).

  

Test connection button

• A Test connection button is now visible in the "Your Own Azure" configuration panel, below the fields.
• The button is enabled as soon as all fields contain a value (format validity is not required to trigger the test).
• On click, a backend call independently validates each of the three resources: Log Analytics Workspace accessibility, Application Insights Connection String validity, and App Registration authentication (Client ID + Secret).

Test result display

• On full success: a green result block is shown with a per-resource status row (green check per item).
• On partial or full failure: a red result block is shown with per-resource detail and a human-readable failure reason per row (e.g. "Invalid Client ID", "Workspace unreachable")
   

 Background

The analytics filter configuration panel mixed two distinct concepts — defining what data is tracked and deciding whether to expose it as a filter — without a clear separation. The result was a confusing interface that required unnecessary choices during property creation and obscured the primary purpose of the screen.

What's new

Labelling & page-level changes

• The main page title is renamed from "Analytics filter properties" to "Tracked data & filters".
• A description is now displayed below the title: "Define the list of properties you track in analytics and if you want to use them as filters in displayed results. When you decide to track a property, the information will be stored in the analytics application (App Insights)."
• The "Create analytics filter property" button is renamed "New tracked property". The associated right panel title becomes "Add tracked property" (previously "Create property").
• In the Feature Dashboard manage panel, the "Manage filters" section is renamed "Tracked data & filters" and the "Filters" button is renamed "Manage".
  
   

Tab system replacing the Source column

• The Source column is removed from the table. Properties are now separated by type via two tabs above the table: User filter and Content filter.
• The "New tracked property" button sits on the same row as the tabs and is tied to the active tab. Clicking it from the User filter tab creates a user property; from the Content filter tab, a content property. The source selection field is removed from the creation form.
  
  Table column changes
• "Used as filter" column renamed to "Is filter".
• "Based property" column renamed to "Internal name".
• The Is filter column now aggregates default value information inline when the filter is enabled — displayed as: ON (default values: X, Y, Z…). The separate "Default values" column is removed.
• The on/off toggle in the table is replaced by a read-only status indicator (ON / OFF). Filter toggling is managed in the create and edit forms, not in the table.
   

Create / Edit property form

• Form title updated to "Add tracked property" / "Edit tracked property".
• "…selection" labels simplified by removing the word "selection" in two places.
• Display name field moved directly under the user property field.
• An "Is filter" option is added below the display name field. When enabled, a default value field appears immediately below it. The default value field is hidden when the filter is off.
   

Background

In modern experience multilingual environments, each language variant of a page was previously tracked as an independent entry in advanced analytics. This fragmented view made it difficult to assess the real reach and engagement of a piece of content.

 

What's new

Aggregated master content view

• Pages are now grouped by their master language version in the analytics table.
• Metrics (views, likes, and other engagement data) are aggregated across all language variants and displayed against the master entry. Aggregation is performed client-side to ensure totals stay consistent with individual language breakdowns.
• The master page title is displayed as the primary label, rather than the internal page name.

Language drill-down

• Each master entry can be expanded to reveal per-language results, including the master language itself.
• Sub-language rows display only the language code (e.g. EN, FR) — no page title is shown at this level.
• If no data exists for a given language variant, it still appears in the list with zero values to preserve consistency across the board.

Language filter behaviour

• When a specific language is selected in the filter, the grouped view is preserved. Only the selected language appears in the sub-language list, and the master total reflects that language's data.

Scope

• This feature covers modern experience multilingual sites only.
• Powell Var  is out of scope, as its analytics operate at multi-site level rather than per-site.

The knowledge base detail view now displays the list of agents connected to it, directly in the configuration panel, without needing to open each agent individually.

 This gives administrators full visibility into which agents will be affected before making any changes to a knowledge base, reducing the risk of unintended impacts on live configurations.

Buddy agents can now generate charts on demand,  no additional configuration required. 

When a user requests a visual breakdown, or when the agent determines that a chart would make a response clearer, it automatically produces the appropriate visualization. 

Charts can be generated from knowledge base content, user-uploaded attachments, or the model's own knowledge.  Over 8 chart types are available, and every generated chart can be downloaded for reuse outside of the agent interface.