Overview

Customer Portal access settings let you keep your portal public or restrict it to your team and approved customers. You can grant private access through email invitations, allowed email domains, customer identification, or a supported identity provider.

These settings apply across the Workspace's brands. They are separate from category and Request visibility, Roadmap access, and Help Center privacy controls, which limit what a permitted person sees.

Choose public or private access

1. Go to Settings → Customer Portal → Access

2. Under Customer Portal visibility, choose Public portal or Private portal

3. Review the effects shown in the confirmation

4. Click 'Change privacy setting'

Visitors can open a public portal, while individual content can still have its own restrictions, such as access limited to a user segment. A private portal requires permitted access. After you make it private, the SDK identification, Allowed users, and Identity providers sections appear so you can configure at least one access method for your customers.

Give customers private access

Invite specific email addresses

1. Under Allowed users, open Invite specific email addresses

2. Click 'Invite new users'

3. Enter the customer email addresses

4. Turn on Send email notification to email each customer a link to the portal, then send the invitations

Invited addresses gain access as soon as you send the invitations, with or without the email. Use 'View invited users' to open the Users directory.

Allow an email domain

1. Under Allowed users, open Give access to specific email domains

2. Enter one or more domains such as example.com, separated by commas and without @

3. Click 'Add'

Use the remove control beside a domain to remove that access route.

Identify customers from your app

Use SDK identification when customers should enter Featurebase with their existing app identity. Follow the identification setup guide, including identity verification for private access.

Connect an identity provider

Under Identity providers, open Enable access by Microsoft Entra ID and click 'Connect with Microsoft Entra ID'. This grants portal access to users verified through the connected tenant.

If the control is unavailable, use the live chat link shown in the setting to contact Featurebase.

Connect customer single sign-on

Customer single sign-on (SSO) sends customers through your application's authentication flow. Follow the web portal SSO setup guide to implement the flow before enabling it.

Under Customer SSO, enter the implementation's Sign-in URL and click 'Save'. Test the full journey from the portal to your app and back as a customer.

Check access across portal pages

Test the portal as a customer with a permitted account and with a signed-out visitor. Check the menu and direct links to the categories, Requests, Roadmaps, and help content you use.

FAQs