Glassdoor User Management Guide

• Model type: role-based
• Description: Glassdoor Employer Center uses a role-based model with at least two tiers (Admin and standard user). Admins control user access. Granular per-feature permission toggling is not publicly documented.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Coarse - role assignment at account level; no documented per-feature permission toggles for individual users.

1. Log in to Glassdoor Employer Center at glassdoor.com/employer.
2. Navigate to Account Settings (top-right menu or account dropdown).
3. Select 'User Management' or 'Manage Users'.
4. Click 'Add User' or 'Invite User'.
5. Enter the new user's email address and assign a role (Admin or Standard User).
6. Send the invitation. The invitee receives an email to accept and set up access.

Required fields: Email address, Role assignment

Watch out for:

• Only existing Admins can invite new users.
• Invitees must have or create a Glassdoor account using the invited email address.
• If the invitee already has a personal Glassdoor account with that email, they will access the Employer Center through the same login.
• No SCIM provisioning is available, so user lifecycle must be managed manually.

• Can delete users: Unknown
• Delete/deactivate behavior: Glassdoor's public help documentation does not clearly distinguish between deactivating and permanently deleting an employer user. Removal appears to revoke access to the Employer Center; whether the underlying Glassdoor account is deleted is not documented. Exact behavior is unverified.

1. Log in to Glassdoor Employer Center.
2. Navigate to Account Settings → User Management.
3. Locate the user to be removed.
4. Select 'Remove' or 'Revoke Access' next to the user's name.
5. Confirm the action when prompted.

Watch out for:

• No SCIM means removing a user from Okta or Entra ID does NOT automatically revoke Glassdoor Employer Center access; manual removal is required.
• If SSO is not enforced, a removed IdP user may still log in with a username/password.
• Removing the last Admin locks the account; a new Admin must be designated before removing the current sole Admin.
• Offboarding workflows must be manual due to absence of SCIM or directory sync.

• Where to check usage: Employer Center → Account Settings → User Management (lists active users with roles)
• How to identify unused seats: No automated inactive-user reporting is documented. Admins must manually review the user list and cross-reference last login activity if visible.
• Billing notes: Glassdoor employer pricing is fully custom and negotiated directly with the Glassdoor/Indeed sales team. No self-serve seat add/remove billing is available. Seat changes likely require contract amendment. Renewals have been reported to include ~10% uplift.

Because Glassdoor has no SCIM or user-management API, offboarding a departed employee requires a separate manual step in the Employer Center regardless of what your IdP does. Revoking access in Okta or Entra ID stops future SSO logins only if SSO is enforced - it does not remove the Glassdoor account record.

If the sole Admin leaves the organization, account recovery requires a support ticket to Glassdoor. There is no self-serve fallback, and no documented inactive-user reporting to help Admins identify stale seats proactively.

Practitioners consistently flag three friction points with Glassdoor employer administration. First, offboarding is a manual gap: IdP deprovisioning does not cascade to Glassdoor, so departed employees can retain access if the Employer Center step is missed.

Second, audit visibility is limited - the UI provides sparse activity logging, making it difficult to verify who accessed the account and when. Third, any seat or plan change requires direct engagement with the Glassdoor/Indeed sales team; there is no self-serve billing adjustment.

Common complaints:

• Users report that removing a departed employee's Glassdoor Employer Center access requires manual steps and is not automated through SSO/IdP offboarding due to lack of SCIM.
• Admins note difficulty recovering account access when the sole Admin leaves the company, requiring support ticket escalation.
• Employers report limited transparency into which users have accessed the Employer Center and when, due to sparse audit/activity logging in the UI.
• Community feedback indicates Glassdoor's employer admin UI is considered basic compared to competing employer branding platforms, with limited role granularity.
• Pricing opacity and requirement to contact sales for any seat or plan changes is a recurring friction point cited by HR and IT admins.

Glassdoor is an employer branding and review-management platform, not an identity-integrated SaaS tool. Its admin model is functional for small, stable teams but creates compounding overhead as headcount changes.

The absence of SCIM means every app offboarding checklist must include a manual Glassdoor step - a gap that is easy to miss and difficult to audit after the fact.

Organizations with frequent role changes or strict access-review requirements should factor in the manual overhead before expanding the user roster. Pricing is fully custom and enterprise-only; smaller organizations are explicitly noted as a poor fit.

Bottom line

Glassdoor Employer Center delivers employer branding and review management under a simple two-role permission model, but it carries a meaningful operational cost for IT and HR teams: no SCIM, no user-management API, no automated offboarding, and no self-serve seat management.

Every user lifecycle event - add, remove, or role change - requires a manual action by an Admin inside the Employer Center UI, and a single point of failure exists if that Admin departs without designating a successor.

Teams that prioritize clean access hygiene should treat Glassdoor as a high-touch exception in their offboarding runbooks.