Privacy Settings

Every organization can control which trace visibility levels are allowed for members when publishing.

Open privacy settings

1. Go to the organization profile (for example, https://traces.com/acme).
2. Open Settings.
3. Open the Privacy section.

Only org admins can change these settings.

What you can configure

• Allowed publish visibility levels
  • Toggle which of public, direct, and private are allowed in your org.
  • When a level is disabled, publishing with that level is blocked.
• Default visibility for new shares
  • Set the default visibility used when traces share is run without --visibility.
  • This helps enforce consistent collaboration defaults.

Publishing behavior with restrictions

• If a teammate tries to publish with a disallowed visibility, the publish action will fail with a validation error until a valid level is used.
• Disallowed levels are enforced at the namespace (org) level, not just in the CLI.
• Personal namespaces are not affected; they follow the regular personal defaults.

Practical workflow

1. In an org where external sharing is limited, disable public.
2. Optionally keep private enabled for collaboration inside the org.
3. Keep direct enabled when link-based sharing is still desired.
4. Save changes.

After changing privacy settings, members will see the new defaults and restrictions reflected when publishing new traces.