Your roster, always current

Authenticate with your tenant, choose which groups to sync, map directory fields to your roster schema, and run — setup takes minutes. Incremental delta sync fetches only what changed; group scoping syncs just students, just staff, or just contractors, not your whole tenant; extension attributes (card UIDs, boarding status) flow through automatically; and users removed from a synced group are deactivated, not deleted, so you keep the audit trail and can reactivate. Available on Pro plans and above.

Point a master list at one Airtable base and table, map the fields you want, and your records appear in CaptrID. Photos stored in attachment fields sync natively — no separate capture step. Run a manual sync on demand, and webhooks pick up changes as records are edited in Airtable, so the roster stays current without re-importing. Ideal for membership directories, volunteer lists, and any team already running their people data in Airtable.

Want your identity provider to push changes directly? CaptrID supports SCIM 2.0, the industry standard for automated provisioning — when someone joins, changes department, or leaves in your IdP, the change reaches CaptrID within seconds. Works with any SCIM 2.0 provider, including Okta, Microsoft Entra ID, PingOne, OneLogin, and JumpCloud. Connect your IdP, copy the SCIM URL and bearer token, and assign users or groups — default schema fields and mappings are created for you, and a token per master list lets you sync different groups to different lists. Available on Business and Enterprise plans.

No directory provider? Upload a CSV, map columns to your roster fields, and import. CaptrID validates the data, flags duplicates, and handles type mismatches before anything is written. It uses the same field-mapping and transformation pipeline as directory sync, so a spreadsheet export, an SIS dump, or a manual list all land cleanly in the same master list.

Every sync source — directory API, Airtable, or CSV — uses the same field-mapping system. Map source fields to your roster schema, apply transformations (lowercase, uppercase, trim, direct copy), and set which field is the unique identifier for matching. Mapped fields are protected from accidental manual overwrites; unmapped fields (locally-added notes or tags) are preserved across syncs. You control which fields the source owns and which you manage locally.

When a session captures photos or updates data, those changes don't overwrite your roster automatically. CaptrID generates a changeset — a field-by-field review with conflict detection — and you approve or reject each change before it applies. If the same person was updated in both the session and the master list since the snapshot, both values are shown side by side: choose the session value, keep the master value, or skip the field. Applied changesets can be rolled back.

Native Google Workspace sync is in progress (Workspace customers with a SCIM-capable IdP can provision today). Directory write-back is also coming — pushing a captured card serial or approved photo back to your directory, e.g. writing a card UID as an Entra extension attribute so access control picks it up. And for anything bespoke — an HR platform, student information system, or membership database with an API — we build custom integrations.