{"version":"2.1.234","anchor":"publishable-artifacts-are-no-longer-described-as-org-only","canonical_anchor":"publishable-artifacts-are-no-longer-described-as-org-only","heading":"Publishable artifacts are no longer described as org-only","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/publishable-artifacts-are-no-longer-described-as-org-only","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Publishable artifacts are no longer described as org-only\n\nArtifact guidance no longer wrongly says declaring publish capability limits a page to your organization.\n\n**What**\n\nThe artifact review and workshop skill prompts were corrected: declaring publish capability on a page does not restrict it to people inside your organization. Only a page wired to a live connector-backed signal still cannot be shared externally.\n\n**Details**\n\n- The choice presented to users is now \"live signal (org-only)\" versus \"no live signal\", rather than interactive versus static.\n\n**Evidence**\n\n`the artifact-publish capability alone carries no such limit`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}