Organization Owners can prevent accidental public publishing and sharing with people outside the organization. Open Settings → Organization → Security and use the controls under External access.
Allow public artifacts
Turn this off to stop anonymous access to every owned artifact whose stored visibility is Public. Members of the publishing organization can still open those artifacts after signing in. Publishers must choose Company or Private for new artifacts and updates while the restriction is active.
Existing artifacts keep their Public visibility label. This makes retained state visible for review and means they become public again if an Owner later turns the setting on. Use Review public artifacts before re-enabling access.
Allow public artifacts also controls whether people outside the organization can make copies of its public artifacts. Disabling it blocks new outside copies; it cannot recall independent copies already created. No separate copy setting or additional plan requirement applies.
Allow sharing outside the organization
Turn this off to stop guest access and prevent adding new outside email recipients. Existing recipient entries remain visible and removable, but they do not authorize access while the restriction is active. Organization members and addresses from verified organization domains remain available.
This setting does not stop an Owner from inviting someone as an organization member. Membership is a separate, explicit access boundary.
Show document titles in restricted link previews
This setting is available in organizations that use Spaces and starts on. When someone shares a restricted Space document link in a chat, anyone who sees the preview can read the document title. Opening the document still requires access.
Turn the setting off to show Shared document when a chat app fetches a fresh preview from Display. A chat app can reuse a preview it already fetched, even in a new message. If you turn titles back on, the change can take time to reach new previews. Owners can change this setting on every plan. The setting controls the title in the preview text and image. A shared URL can still contain a title-derived slug.
Availability and plan changes
Turning off public artifacts or outside sharing requires Business or Enterprise. A restriction remains active if the organization later moves to another plan. Any Owner can turn access back on, including after a downgrade.
When public artifacts remain disabled on Free, new Company and Private content still uses the plan's gated-artifact allowance. At the limit, delete a gated artifact, upgrade, or ask an Owner to allow public artifacts again.
When a change takes effect
New publishes, updates, invitations, and guest credentials are blocked as soon as the database change commits. Existing public and guest access normally stops within one minute as the setting reaches the edge.
Display cannot recall content that a viewer already downloaded or that an older browser or shared cache retained. If the Security page says a change still needs to be applied, retry the same setting; no additional audit event is created for a repair.
Recover from a blocked action
- For
public_artifacts_disabled, choose Company or Private, or ask an Owner to enable public artifacts. - For
external_sharing_disabled, remove outside recipients, or ask an Owner to enable outside sharing. - Owners change these settings only in the dashboard. The CLI and MCP tools do not expose policy-management actions.
See Sharing and access for artifact-level audiences and Plans and limits for gated-artifact limits.
Spaces access
For an organization that uses Spaces, inspect the file or folder's Share panel to see direct and inherited access. A Shared Space can require membership in addition to a file grant. Removing one grant does not remove access inherited from another source.
Organization public-access and outside-sharing restrictions still apply. The CLI and MCP do not change organization security policy. See Spaces and files.
Discussions in Spaces
Commenting follows current file authority and the organization’s access policy. It requires Commenter access or higher. A verified outside person with eligible access can participate. A view-only invitation does not grant comment controls.
With Anyone with the link → Can comment or higher, anyone possessing the link can read existing and future discussions, including resolved threads, replies, display names, and avatars. Email verification to view does not hide these public discussions. Visitors sign in or create a Display account before writing; this does not add organization membership. Viewer link access does not expose discussions.
Forwarding the link forwards discussion access. Display names can identify people, including names based on email addresses. Disabling public access or narrowing the link grant stops new reads under the ordinary access-change timing; content already received cannot be recalled.
An organization key needs its own eligible grant and writes as that key. Organization roles do not grant private-content access. Removing access also removes discussion authority, including for retries and personal watches. See Review comments.