{"version":"2.1.293","anchor":"org-forced-settings-new-uuid-validator-and-config-reference","canonical_anchor":"org-forced-settings-new-uuid-validator-and-config-reference","heading":"Organization IDs in managed settings are now checked for format","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/org-forced-settings-new-uuid-validator-and-config-reference","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Organization IDs in managed settings are now checked for format\n\nManaged settings now check that an organization ID is a valid UUID, and documentation links appear only for settings the desktop app reads\n\n**What**\n\nIn managed deployments, an organization's administrators can enforce settings for everyone. Two things changed for these settings:\n\n- An organization ID is now checked to be a UUID, a standard long identifier. Spaces around it are trimmed and letters are made lowercase. A bad value is rejected with the message \"expected an organization UUID\".\n\n- Links to the configuration reference documentation are now made only for published third-party settings that the desktop app reads. Before, any published third-party setting got one.\n\n**Why**\n\nThis affects how managed deployments set which organizations are allowed. A mistyped organization ID now fails the check instead of being accepted.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: yes"}