{"version":"2.1.227","anchor":"more-accounts-qualify-for-memory-sync","canonical_anchor":"more-accounts-qualify-for-memory-sync","heading":"More accounts qualify for memory sync","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/more-accounts-qualify-for-memory-sync","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### More accounts qualify for memory sync\n\nMore accounts now qualify for memory sync through an extra OAuth-scope path.\n\n**What**\n\nThe check that decides whether memory sync is available gained an extra way to qualify: an account on a first-party base URL with the right OAuth scopes now passes even if the previous conditions do not.\n\n**Details**\n\n- Still requires the `allow_memory_sync` compliance permission, which is denied under HIPAA and zero-data-retention modes.\n- The added branch is one of three alternatives; exactly which accounts the third branch admits is not fully determined by the code.\n\n**Evidence**\n\n`allow_memory_sync`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}