Answer: To trigger a full re-sync in OneLogin after fixing the email mismatch, go to the app's Provisioning tab, look for a Re-sync or Sync All option and run it. An incremental sync will not update existing records after you change an attribute mapping, so a full restart of the provisioning cycle is required. Status: Confirmed Entry: tool/claude-apps/admin-and-enterprise/onelogin-full-resync Revision: 2 Digest: sha256:cd79824aed9019ee (changes whenever the content changes) Timeline: Created: 2026-11-13T02:59:05Z Last changed: 2026-11-20T12:05:16Z (Incremental sync limitation: — → An incremental sync will not update existing records after you change an attribute mapping.) Last verified: 2026-11-20T12:05:16Z Next check: 2026-11-21T12:05:16Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Action | Re-sync or Sync All | [1] | 2026-11-20 Location | Provisioning tab | [1] | 2026-11-20 Sync type required | full restart of the provisioning cycle | [1] | 2026-11-20 Incremental sync limitation | An incremental sync will not update existing records after you change an attribute mapping. | [1] | 2026-11-20 Individual reprovision option | Re-provision | [1] | 2026-11-20 Sources: [1] Anthropic. "OneLogin SSO/SCIM email mismatch | Claude Help Center". https://support.claude.com/en/articles/13917861-onelogin-sso-scim-email-mismatch Role: primary. Accessed: 2026-11-20T12:05:16Z Quote: "look for a Re-sync or Sync All option and run it" (Supports: Action) Quote: "In the app's Provisioning tab" (Supports: Location) Quote: "You must trigger a full restart of the provisioning cycle." (Supports: Sync type required) Quote: "An incremental sync will not update existing records after you change an attribute mapping." (Supports: Incremental sync limitation) Quote: "find the Claude app, and use Re-provision" (Supports: Individual reprovision option) Snapshot SHA-256: 73dff3f14b3dc8df2b3afa97d63f87da820f261182baaeb554fbd9eda707faba (captured 2026-11-19T12:01:47Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:01:47Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:05:16Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:05:16Z Last attempt: 2026-11-20T12:05:16Z Notes and limitations: Extracted automatically from a single official source (section "Trigger a full re-sync"). Related: https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-sso-prerequisites What do I need before setting up OneLogin SSO for Claude? https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-verify-sso How do I verify that OneLogin SSO is working for Claude? https://latestn.com/tool/claude-apps/admin-and-enterprise/open-security-center How do I open the security center in Claude Enterprise? https://latestn.com/tool/claude-apps/admin-and-enterprise/okta-sso-prerequisites What are the prerequisites for setting up Okta SSO with Claude? https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-configuration-values-location Where do I find the Audience, ACS URL, and SCIM credentials for Claude OneLogin setup? https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-enable-scim-provisioning How do I enable SCIM provisioning for Claude in OneLogin? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:05:16Z | changed | Incremental sync limitation: — → An incremental sync will not update existing records after you change an attribute mapping. | [1] 2026-11-13T02:59:05Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-full-resync/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/onelogin-full-resync POST: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/onelogin-full-resync with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-apps/admin-and-enterprise/onelogin-full-resync?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I trigger a full re-sync in OneLogin after fixing the email mismatch for Claude? Revision 2, last verified 2026-11-20T12:05:16Z. https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-full-resync (accessed 2026-11-21T10:06:16Z). @misc{LatestN_tool_claude_apps_admin_and_enterprise_onelogin_full_resync_r2, title = {How do I trigger a full re-sync in OneLogin after fixing the email mismatch for Claude?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-full-resync}}, note = {Revision 2; digest sha256:cd79824aed9019ee; last verified 2026-11-20T12:05:16Z; accessed 2026-11-21T10:06:16Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-apps/admin-and-enterprise/onelogin-full-resync