article updated 8th June 2026
The WorkPoint Express 365 June 2026 Update includes new functionality to support Drag and Drop actions plus general improvements to product usability and efficiency as described in the release notes here.
In this article - we will discuss the new permissions that WorkPoint Express 365 requires to support these functions and how you can minimize impact for your users on deployment.
About this release
As WorkPoint Express 365 is a modern Office Add-In in most cases when we release updates to the application - new functionality and fixes are instantly available to all existing users. We publish the application updates to our servers, then Add-in Task Pane on users' desktops will automatically recognize that a new version is available and reload it with zero interruption.
On this release however, new functionality relating to the new Drag and Drop features and how we store users' application preferences and state do require additional tenant permission scopes to use the new functionality. All
For customers that are already running WorkPoint Express 365, this means that we need to request consent from a tenant administrator to use these new functionality. Once these permissions are granted - the new functionality be instantly available on release.
For new customers, after the release - will be submitting the updated application manifest to Microsoft for review. This is simply to explicitly declare these permissions as dependencies as part of the Office Add-In listing. Once Microsoft review and approve this update, the store listing will show these permissions as pre-requisites and new installations will prompt users to grant consent accordingly.
What do I need to do?
For existing customers, the updated application will begin requesting additional permissions to support the new functionality as soon as it the release is deployed. If these permissions are not already granted, users will start to see a consent prompts as Express 365 requests an application token with the new scopes.
Although technically, the permissions requested by WorkPoint 365 do not require Admin Consent, tenant restrictions will typically block users for consenting to all but very basic permissions for applications from verified publishers such as WorkPoint (see ms.learn for more details).
This means that in most tenants, unless the permissions are pre-approved by an administrator regular users will receive the "Need Admin Approval" consent dialog (2 below) instead of the "Permissions Requested" alternative (1) if a users are allowed to approve all the permissions WorkPoint Express 365 requires.
Even if the User Consent option is available in your tenant, such prompts can disrupt users and create uncertainty about whether the requests are expected.
To provide a controlled and predictable rollout, it is recommended that permissions are granted centrally by an administrator.
You can grant consent in one of two ways:
1. Before release using consent link (recommended)
The following hyperlink is a direct link to the consent approval for the WorkPoint Express 365 Application Registration. If opened by a tenant administrator with privileges to administer cloud application (per MS Learn article here), they can review and grant consent for the incremental scopes on behalf of the organisation.
https://login.microsoftonline.com/organizations/adminconsent?client_id=6aa890f6-1f83-4e1f-a5fe-5e20bdc5cc85&redirect_uri=https://express365.workpoint365.com/
This link can be shared and used at any point before the WorkPoint Express 365 release. If approved, this means that Express 365 will already have the necessary permissions before the updated release is deployed by WorkPoint resulting in zero inconvenience or confusion among the users.
2. After release interactively:
Alternatively, after the release is deployed - if an administrator with the privilege to grant tenant-wide admin consent (per article here) opens WorkPoint Express 365 - the interactive consent prompt will provide the extended option to "Consent on behalf of your organisation" (per 2 in the screenshot below). Checking this box and clicking "Accept" will grant the necessary permissions for all users and avoid the inconvenience of individual user consent prompts.
While the above interactive admin consent will grant the required permissions and suppress consent prompts for all users - it would require that an administrator is among the very first users to access WorkPoint Express 365 after the release. Depending on user patterns, this might be hard to predict. WorkPoint therefore recommend that the consent link approach is used prior to the release to minimize user inconvenience and confusion.
New Permissions
For reference, the table below provides the details of the new permissions that WorkPoint Express 365 is requesting as part of this update.
| Permission | Description | Type | Requires Admin Consent | Used For | Description |
|---|---|---|---|---|---|
| Files.ReadWrite > Files.ReadWrite.All | Allows the application to have full access to all files user can already
access. | Delegated | No | Supporting Simple File upload via Drag and Drop | With the June 2026, WPE365 now supports Drag and Drop actions. Users can now drag Emails and Attachments from the Outlook Mail host to Drop Zones on WorkPoint Business Modules, Entities and Document Libraries. In addition to the existing WorkPoint Automate-based upload, WorkPoint Express 365 now supports direct drag and drop of emails and attachments from Outlook into libraries, using File.ReadWrite.All (delegated) to upload .eml files and attachments on behalf of the user, constrained by their existing SharePoint permissions. You can read more about how WorkPoint Express 365 uses this permission to for simple email and file upload in the support article here. |
| User.Read > User.ReadWrite | Allows the app to update the profile properties for the signed-in user's
work or school account | Delegated | No | Storing user preferences and application state using Microsoft Graph Open Extensions API. | Prior to this release, WorkPoint Express 365 stored application state (e.g. Last Viewed Entity) and user preferences (e.g. Preferred Business Module View) in browser local storage specific to the Outlook host. To support cross-host scenarios (Word, Excel, PowerPoint), this data is now stored as Microsoft Graph extension data enabling per-user, cloud-based persistence.Preference and state data is written and retrieved via the graph endpoint which requires User.ReadWrite access to manipulate. https://graph.microsoft.com/me/extensions/com.workpoint.express365.preferencesIf this permission is NOT granted, WPE365 will gracefully revert to using local/browser web storage. State settings will be unique with each host application. |
Comments
0 comments
Please sign in to leave a comment.