Skip to main content
Question

Locking down portals by domain (not account-wide) - any workarounds?

  • February 12, 2026
  • 0 replies
  • 0 views

Hi all -

 

We’re in the process of rolling out multiple Freshdesk portals for different customer groups (like Client Support v Internal Support v Partner Support, etc), and we’re running into limitations with portal access control being applied to broadly at the account level. 

 

What we’re trying to accomplish: 

  • Create separate portals for different customer groups/segments
  • Restrict portal access by domain (e.g., only @companyA.com can access portal A, only @companyB.com can access Portal B).
  • Avoid making those domain restrictions apply globally across the entire Freshdesk account

The issue is that Freshdesk’s access control seems to apply at the account level, not per-portal, which makes it hard to lock down one portal to a specific customer group while still keeping other portals accessible to different domains.

 

Has any successfully:

  • Scoped portal access by domain on a per-portal basis?
  • Used SSO, custom login flows or any creative workarounds to segment portal access?
  • Built multiple customer portals for different customer groups without splitting into multiple Freshdesk instances?

I’d love to hear what has work for you (or what didn’t work for you). Trying to avoid standing up entirely separate Freshdesk instances.

 

Thank you!