E
Enoch Leffingwell
Context
The Meta Muse connector for HighLevel (launched September 29, 2026) connects through HighLevel OAuth. During connect, the user picks which sub-accounts to grant access to.
Problem
Agency users get a bulk/company token and can multi-select several sub-accounts in one connection. Sub-account users get a location token and can only select ONE sub-account per connection, even when they are legitimate users of multiple sub-accounts. To switch sub-accounts they must disconnect, reconnect, and re-authenticate every time, then keep track of which location is currently connected. For team members working across two or more sub-accounts daily, this makes the connector painful to use.
Example: a team member with user access to two sub-accounts (Heavenly Leaves and Remedies at Law) cannot connect both to her Muse. She connects one, and reaching the other means a full disconnect/reconnect cycle each time.
The only workaround is the agency owner signing into HighLevel with the owner's login inside the team member's Muse app, which hands the team member owner-level permissions. That is a security tradeoff no agency should have to make.
Request
Allow one Muse user to authorize multiple locations and switch between them inside the connector, either by:
  • letting sub-account users multi-select all locations they have access to during the OAuth install (the same picker agency users get), or
  • letting a Muse user hold several location grants (one per sub-account) and choose between them without reconnecting.
Why it matters
Agencies run teams across sub-accounts. Fencing each person to one location at a time sharply reduces the value of the Muse connector for exactly the multi-location operators HighLevel is built for.