PalveronPalveronDocs
User Handbook

Configure Identity Provider

Connect Entra ID or Google Workspace — user import via OAuth, group-to-role mapping, deactivation on removal.

Wire your identity provider into Palveron and stop maintaining the member list by hand — users are imported from your directory, group membership maps to permission levels, and users removed from mapped groups are deactivated on the next sync.

Supported providers

ProviderConnectionUser sync
Microsoft Entra IDOAuth (read-only directory scopes)✅ import + periodic sync
Google WorkspaceOAuth (read-only directory scopes)✅ import + periodic sync
OktaRoadmap — not yet available

Palveron connects via a read-only OAuth authorization of your directory (users and group memberships). SCIM push provisioning is on the roadmap and not yet available — there is no SCIM endpoint or SCIM token today. If a setup guide asks you for one, it is outdated.

Setup takes about 10–15 minutes; ongoing maintenance is zero.

Generic flow (any provider)

  1. Open Team → Identity Provider (visible to owner and admin only).
  2. Click Connect provider and pick Entra ID or Google Workspace.
  3. You are redirected to your provider to authorize read-only directory access.
  4. Map IdP groups to Palveron permission levels.
  5. Click Start synchronization.

The platform imports users from every mapped group, then keeps them in sync periodically. Each user lands in the role corresponding to their IdP group.

Entra ID (Azure AD)

  1. In Palveron, open Team → Identity Provider → Connect → Entra ID and enter your Directory (tenant) ID.
  2. You are redirected to Microsoft to consent to read-only Graph scopes (User.Read.All, GroupMember.Read.All).
  3. The OAuth redirect URI used by the flow is https://gateway.palveron.com/api/v1/integrations/oauth/callback — if your organization restricts consented apps, allow this URI.
  4. Back in Palveron, assign the groups you want to sync (typically Palveron Admins, Palveron Editors, Palveron Viewers).

Google Workspace

  1. In Palveron, open Team → Identity Provider → Connect → Google Workspace.
  2. You are redirected to Google to consent to read-only Admin Directory scopes (admin.directory.user.readonly, admin.directory.group.readonly). A Workspace super-admin should perform this step.
  3. The OAuth redirect URI used by the flow is https://gateway.palveron.com/api/v1/integrations/oauth/callback.

Initial sync runs immediately after connecting; afterwards Palveron re-syncs periodically. Trigger an immediate sync with Sync now.

Map groups to Palveron levels

After the connection succeeds, Palveron lists every group it can read from the IdP. Map each to a permission level:

IdP group (example)→ Palveron level
Palveron Adminsadmin
Compliance & Riskeditor
Engineeringviewer
Salesviewer

Unmapped groups default to viewer (lowest permissions). Members of multiple groups inherit the highest mapped level.

What auto-sync does

After the IdP is connected:

  • New user added to a mapped group → user appears in Palveron at the mapped level (status: ACTIVE).
  • User removed from all mapped groups → user deactivated in Palveron on the next sync (cannot log in; responsibility-chain references trigger reassignment warnings).
  • User moved between groups → role updated on the next sync.
  • User profile updated in the IdP (display name, email) → fields update in Palveron on the next sync.

Synced users carry an IdP badge in the member list. They cannot be removed or role-changed manually — managed entirely through the IdP.

Disconnect the IdP

  1. Team → Identity Provider → Settings (⚙️) → Disconnect.
  2. Confirm.

On disconnect, synced users remain in Palveron but are converted to manually-managed users — they are no longer affected by IdP changes. Their current role is preserved. If you wanted to delete the users entirely, do so in the IdP first, let the deactivation propagate, then disconnect.

Audit trail

Every sync action (user added, role changed, deactivated) is recorded as a TEAM_* governance event. The full sync history is available under Monitoring → Governance Events.

On this page