> ## Documentation Index
> Fetch the complete documentation index at: https://gleanfeed.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure customer accounts

> Require portal sign-in when customers should submit feedback, vote, comment, or react to updates.

Customer accounts let people interact with your portal as known customers instead of anonymous readers. The dashboard label for this setting is **Visitor accounts**.

Workspace owners and admins configure it under **Workspace settings → Portal → Behavior**.

## Team members on your portal

Workspace team members use their existing Glean Feed profile on their workspace's portal. Open **Public Portal** from the dashboard, or sign in to the portal with the same verified email as your team profile. Glean Feed recognizes you as a team member instead of creating another visitor account for that sign-in.

Open the profile menu on the portal to confirm the identity. It shows a **Team** badge, the current workspace role—Owner, Admin, or Moderator—and a **Workspace dashboard** link. Feedback, votes, and comments created from the portal are attributed to the team profile; team comments appear as team replies.

If a team member previously signed in as a portal visitor with the same email, Glean Feed keeps that history attributed to the team profile and removes the duplicate visitor identity from the customer **Members** list.

Choose **View as visitor** from the portal profile menu to preview the signed-out customer
experience without ending your workspace dashboard session. Refreshes remain in visitor mode. Open
**Public Portal** from the dashboard when you want to restore your team identity.

Team members receive notifications through their team profile and dashboard notification settings,
not through a separate customer identity. Customer accounts continue to use **Sign out** normally.

Customer visitor accounts remain separate, workspace-specific identities. A customer who signs in through the portal or uses [signed widget identity](/widget/identity) remains a customer and does not gain a workspace team role.

<Check>
  Open **Public Portal** from the dashboard. In the portal profile menu, confirm your name, **Team**
  badge, workspace role, and **Workspace dashboard** link appear.
</Check>

## When to enable accounts

Enable visitor accounts when you want customers to:

* Submit requests.
* Vote on requests.
* Comment on requests.
* React to changelog updates.
* Comment on changelog updates.
* Carry a signed session from your product into the widget.

Each action also depends on its matching portal setting. For example, request comments require visitor accounts, Requests in Collect feedback mode, and request comments enabled.

Enable **Visitor accounts**, then turn on only the actions you want: **Request voting**, **Request comments**, **Update reactions**, and **Update comments**. Disabled controls show which prerequisite is missing.

<Check>
  Open the portal in a private browser window. Browsing public content should work without signing
  in. Starting an enabled interaction should prompt the customer to sign in or create an account.
</Check>

## Tracked customer limits

A tracked customer is a real customer identity in your workspace. Glean Feed creates one when a new customer signs in to the portal, uses [signed widget identity](/widget/identity), or is attached to feedback through the [REST API](/headless/feedback#quickstart-submit-through-your-server).

| Plan    | Tracked customers |
| ------- | ----------------- |
| Free    | 50                |
| Starter | 250               |
| Growth  | Unlimited         |
| Plus    | Unlimited         |

Anonymous readers do not count. Workspace team members who use their team profile on the portal do not count, and the sample customers created during onboarding do not count.

When a Free or Starter workspace reaches its limit, existing customers keep their accounts, sessions, feedback, votes, and comments. The portal blocks only the creation of another customer identity. Workspaces that were already above the limit keep their existing customers and data. Owners and admins can review current usage under **Billing** and upgrade when they need more capacity.

## Beta tester invites

Invite-only beta boards use the same visitor account system as the rest of the portal. There is no separate beta login.

When your team invites someone to a beta board, Glean Feed emails them a portal invite. If they already have a visitor account for your portal, signing in with the invited email grants access. If they do not have an account yet, the invite flow lets them create one with the normal sign-in options.

If the workspace has reached its tracked-customer limit, an invited customer without an existing account cannot create one until the workspace upgrades. Existing invited customers can still sign in and use their boards.

Customer visitor accounts must be active invited testers to see invite-only boards, submit feedback to them, or open their approved posts. Workspace team profiles can access invite-only boards directly without being added as testers.

## Anonymous browsing

Customers can browse visible portal content without signing in.

Anonymous readers cannot submit feedback, vote, comment, react, or use signed widget identity.

## Signed widget identity

If your product already has logged-in customers, identify them in the widget with a server-generated HMAC signature. Glean Feed exchanges that signature for customer-specific session credentials so the widget can act as that customer. Never expose the workspace widget secret in browser code.

Use [signed identity](/widget/identity) for the integration details.

## What happens when accounts are off

If visitor accounts are disabled, signed identity calls return an error and the widget falls back to anonymous browsing. Public portal content can still be visible, but identity-backed actions are unavailable.

<Check>
  After disabling **Visitor accounts**, confirm public content still loads in a private browser
  window and that submission and interaction controls are unavailable.
</Check>