01Who this is for
- Marketplace developers, need to add the new file access permission to keep their apps functional.
- Businesses that use third party tools to display email attachments, must reauthorize those tools to maintain access.
- HighLevel users who embed external attachment viewers, benefit from stronger data protection without changing their in platform experience.
02Secure conversation attachment access, explained
The feature replaces direct attachment links with protected URLs that require explicit permission. When an external application requests an email attachment, HighLevel checks that the app holds the added file access permission and that the request is authenticated. If the checks pass, the app receives the file; otherwise the request is denied.
Secure Conversation Attachment Access lives in the platform’s API layer. It is enforced for email conversation attachments in the first rollout. Future phases will extend the same model to other conversation channels and file based custom fields. Existing direct links keep working only until the migration deadline, after which only the new permission based flow is supported.
03How businesses use secure conversation attachment access
- Marketing agency. The agency’s reporting tool pulls email attachment thumbnails to show clients. After adding the file access permission, the tool authenticates each request and uses the new protected URL format to retrieve the images.
- Legal services firm. A document review app fetches signed contracts from conversation threads. The firm updates the app’s permission set, reauthorizes client accounts, and changes its API calls to include authentication headers for the new URLs.
- Healthcare provider. An HIPAA compliant portal displays patient lab results sent via email. The provider adds the required permission, ensures the portal reauthorizes users, and modifies its integration to request attachments through the secure endpoint.
04The numbers and rules that matter
- Update required by November 30, 2026.
- Existing attachment links work only through the transition period ending November 30, 2026.
05Before you start
- Currently, attachment links are directly accessible without additional permissions, allowing any request with the URL to retrieve the file.
06How to set up and use secure conversation attachment access in HighLevel
Prepare secure attachment access
- Review your integration to confirm it retrieves or shows email conversation attachments outside HighLevel.
- Add the required file access permission to your Marketplace application configuration.
- Modify your code to request attachments using authenticated calls and the new protected URL format.
- Prompt existing users to reauthorize the app so the new permission is granted.
- Run tests to ensure authorized requests return attachments and unauthorized requests are blocked.
- Deploy the changes and verify everything works before the November 30 2026 deadline.
07Settings that matter
- File access permission. Controls whether an external application may retrieve protected conversation attachments via the API.
08Things to know before you rely on it
- The initial rollout covers only email conversation attachments; other channels are planned for later phases.
- Existing direct attachment links remain functional only until November 30 2026.
- Applications that do not access conversation attachments are not required to make any changes.
09How it connects to the rest of HighLevel
- How to select the API version in HighLevel documentation API version guide
- HighLevel pricing and plans Pricing
- Start a 30 day HighLevel trial 30 day trial
Michael's take

In my view, the added permission and authentication step enhances security for apps that need to retrieve attachments.
If your app never accesses conversation attachments, you may not need to make changes.