Artifact Site Anonymous Access and Public Eligibility

Where you see this in the app

This page explains why some artifact-site links open directly for signed-out visitors while others redirect to login or require purchase.

Users encounter this difference when opening share links from posts, copied site links, or public references.

When sign-in is skipped

Anonymous access is only allowed when the site is genuinely public enough to be opened without identity or purchase checks.

From an end-user standpoint, if sign-in is skipped entirely, the app has already decided that anonymous viewing is allowed for that site.

Pricing, audience, and eligibility

The main rules are:

The most important practical rule is simple: if the artifact still requires purchase, anonymous access is not allowed.

Why some links open directly and others do not

Two links can look similar but behave differently because the underlying post rules are different.

That is why one user may see the site open immediately while another is sent to login or told that purchase is required.

The URL alone does not tell the full access story.

What users should check first

Use this order:

1. Ask whether the site is meant to be public at all.
2. Check whether the artifact still requires purchase.
3. Check whether audience restrictions are narrower than a public visitor would satisfy.
4. If the link is public and still fails, compare against revoked or expired-link failures rather than assuming it is only a sign-in issue.

Related docs

• Artifact site access failures: sign-in, purchase, revoked, and expired
• Workspace attachments, published site, and share links
• Post purchase states and access CTAs