Home/HighLevel/Features/Developer Resources/How to set up secure attachment access in HighLevel

Agency, Settings and Integrations

How to set up secure attachment access in HighLevel

In short

Secure Conversation Attachment Access adds a permission based model for external apps that fetch conversation files. Direct URLs are replaced by protected links that require a file access permission and authenticated requests. The rollout begins with email conversation attachments, and developers must update and reauthorize their integrations before the November 30 2026 deadline to avoid service disruption.

AreaDeveloper Resources · Developer Resources
Used forMarketing agency, Legal services firm, Healthcare provider
Setup steps6 steps in 1 task
Last updatedNovember 17, 2026

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

  1. Review your integration to confirm it retrieves or shows email conversation attachments outside HighLevel.
  2. Add the required file access permission to your Marketplace application configuration.
  3. Modify your code to request attachments using authenticated calls and the new protected URL format.
  4. Prompt existing users to reauthorize the app so the new permission is granted.
  5. Run tests to ensure authorized requests return attachments and unauthorized requests are blocked.
  6. 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

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

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.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about secure conversation attachment access.

Will attachments viewed inside HighLevel be affected?

No. Users who open attachments directly in the platform experience no change.

Which conversation channels are impacted by this update?

Only email conversation attachments are affected in the first phase; other channels will be added later.

What happens to current attachment links after the deadline?

Direct links stop working under the old model; applications must use the new permission based access process.

Do existing Marketplace apps need to be reauthorized?

Yes, if they retrieve email attachments. Users must reauthorize the app to grant the added file access permission.

What if developers do not update their applications?

Applications that continue using the old attachment access method may be unable to retrieve protected email attachments after the transition period.

Do applications that do not access conversation attachments need to take action?

No. Applications that do not retrieve or display conversation attachments are not affected.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.