{"version":"2.1.260","anchor":"claudeai-data-import-toggle-no-longer-force-hidden-in-enter","canonical_anchor":"claudeai-data-import-toggle-no-longer-force-hidden-in-enter","heading":"Claude.ai data-import toggle no longer force-hidden in enterprise config UI","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/claudeai-data-import-toggle-no-longer-force-hidden-in-enter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Claude.ai data-import toggle no longer force-hidden in enterprise config UI\n\nThe Claude.ai data-import toggle is no longer hidden in enterprise settings UI.\n\nThe organization\/enterprise config field for \"Claude.ai data import\" is no longer force-hidden in the settings UI; it previously carried a `predicates: { show: () => !1 }` rule that hid it unconditionally, and that predicate has been removed. Its description now spells out the behavior in detail: it lets users import Claude.ai chats and projects, plus earlier Claude sessions on this computer, when `enabled` is true, and notes that `automatic3pImport` is a separate switch. Its egress requirements now also branch on an \"arm\" state (configured vs. default hosts).\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}