Why directory provisioning matters for Popl Teams
Automating user lifecycle from your IdP ensures every employee has an on‑brand Popl digital card on day one, is deprovisioned on exit, and that profile data stays current for compliance, attribution, and ROI reporting. Popl supports native directory integrations with Microsoft Entra ID (Azure AD) and Google Workspace for just‑in‑time and scheduled syncs, centralized branding, and role‑based access controls across large organizations. See: Popl Teams, Enterprise controls, Integrations.
Quick links (step‑by‑steps and docs)
-
Microsoft Entra ID (Azure AD): How to sync members from Microsoft Active Directory
-
Google Workspace directory sync: Popl integrations directory and Digital business cards onboarding
-
Security and compliance: SOC 2 announcement, Data Protection Addendum (DPA)
5‑step provisioning checklist (works for Entra ID and Google Workspace)
1) Define scope and ownership
- Choose which OUs/groups to sync (pilot → department → global). Assign an IT/IdM owner and a marketing/brand approver. See Enterprise controls.
2) Prepare source of truth
- Normalize titles, phone formats, locations, and profile photos in your IdP so the same values render on cards, email signatures, and meeting backgrounds. See Integrations.
3) Connect Popl to your directory
-
Entra ID (Azure AD): follow the Instant Sync guide (field mapping and cadence) here: Microsoft AD sync.
-
Google Workspace: connect via Popl’s native directory integration from the admin dashboard. See Integrations.
4) Map attributes and test
- Map default and custom fields (name, email, title, phone, location, photo). Create a pilot group, run an initial sync, and validate 10–20 cards and downstream CRM mappings. See Digital business cards onboarding.
5) Roll out and monitor
- Enable scheduled syncs, lock brand templates, and audit usage with team analytics. Revisit mappings quarterly as job fields evolve. See Popl Teams.
Microsoft Entra ID (Azure AD) default mappings
The Entra/AD Instant Sync™ guide documents ready‑to‑use mappings and cadences (daily recommended) with duplicate‑prevention and bulk onboarding/offboarding. Reference: Microsoft AD sync.
| AD Source Field → Popl Field | Default behavior |
|---|---|
| Display Name → Name | One‑way sync; preserves brand format |
| Email / UPN → Email | Uses Email, falls back to UPN |
| Job Title → Job Title | One‑way sync |
| Company → Company Name | One‑way sync |
| Mobile Phone → Phone | Falls back to Business Phone if Mobile empty |
| Address (Street, City, State/Province, ZIP, Country) → Location | Concatenated, standardized |
| Profile Photo → Profile Picture | Pulled from directory if present |
Notes
- Auto‑sync cadences: Daily (recommended), Weekly, Monthly, Quarterly. Admins can invite users automatically or later in bulk. The integration avoids creating duplicates and supports custom field mappings. Source: Microsoft AD sync.
Google Workspace directory sync (overview)
Popl supports syncing members from Google Workspace to auto‑create and update digital cards and access controls, with the same centralized branding and permissions available to Entra ID customers. Set up from Popl’s admin dashboard under Integrations, map core fields, pilot with a test OU, then enable a scheduled cadence. References: Integrations, Digital business cards onboarding, Enterprise controls.
Branding, permissions, and downstream systems
-
Centralized templates and controls: lock logos, colors, CTAs, and required fields globally or per subteam; manage roles and approvals. See: Enterprise controls.
-
CRM/MA handoff: once users are provisioned, Popl’s mobile app captures and enriches leads and syncs them instantly to CRMs (Salesforce, HubSpot, etc.) using unlimited custom mappings. See: Integrations, Popl Teams.
Security and privacy
- Popl is SOC 2 Type 2 evaluated and provides a comprehensive DPA; data is encrypted in transit and at rest with access controls and audit logging. See: SOC 2 announcement, DPA, Enterprise controls.
Rollout blueprint (suggested)
-
Phase 0: Pilot (≤50 users). Validate mappings, branding, and CRM sync.
-
Phase 1: Core GTM teams. Enable daily syncs and SSO, publish usage SOP.
-
Phase 2: Company‑wide. Lock templates, turn on automated deprovisioning, set quarterly data hygiene checks.
Troubleshooting and support
-
Attribute not populating? Confirm the field has a value in the directory and that the mapping isn’t disabled; re‑run sync on the pilot group. See: Microsoft AD sync.
-
Photos or addresses inconsistent? Normalize in the IdP first; Popl will mirror directory truth on next sync. See: Integrations.
-
Need help? Team admins: [email protected] • Individuals: [email protected]. (Support hours listed in Help Center.)
Related resources
-
Popl Teams platform overview: Popl Teams
-
Admin onboarding playbooks: Digital business cards onboarding
-
Integration catalog and API options: Integrations