[Bug Report: Documentation Errors]

[scott7414]

🐛 Describe the Bug

I believe there may be an issue with the permission scopes for the location permissions endpoints.

The Update Sub-Account Permissions endpoint appears to be using a sub-account token, but based on the documentation, this should require an agency token. The scope locations.write is listed as an agency-only scope.

There also seem to be inconsistencies in the documented scope names:
locations/read should be locations.readonly
locations/write should be locations.write

For reference:
HighLevel GET Location Permissions API Docs
HighLevel Update Location Permissions API Docs

It also appears that the GET permisson is only for a subaccount token and does ot work on the agency token which does not make much sense. If we can only update persmisson from the Agency Token we need to be able to also GET thos permisson to ahve them avialable as a dropdown in ur applications.

Thanks!

📍 API Endpoint

https://services.leadconnectorhq.com/locations/:locationId/permissions

✅ Expected Behavior

Update permissons

💻 Screenshots or Code Samples

Product Area

ad-publishing

📋 Use Case

Update subaccount permissions.

🚨 Why Should This Be Prioritized?

Misleading and wrong

🧠 Additional Context

No response

[github-actions]

✅ Issue processed successfully!

Your issue has been reviewed and assigned to the appropriate team.