Skip to content
Onact.Create an action ↗

← Help center

PRODUCT GUIDE

Public, unlisted and private visibility

Compare public, unlisted and private actions, understand team access, and choose an audience before sharing a group request.

Updated November 9, 2026 · 3 min read

Visibility determines who can discover or open an action. Public, unlisted and private are different controls. Public actions can appear in Explore. Unlisted actions can be opened by anyone who obtains the URL, including through forwarding. Private workspace actions require an authorized member or owner. Choose visibility before collecting responses, and explain the audience in the invitation itself.

Public discovery

A public action is suitable for information you intend other visitors to see. Search, discovery cards and shared links can expose its title and description. Do not put private addresses, account records or confidential participant details into a public action merely because you plan to share it with a small initial group. A public page being hard to find does not make it private. Screenshots and copied text can travel outside the platform. Review options, response labels and related links from the perspective of someone arriving without context. Reports and moderation can address inappropriate content, but they cannot reverse information already copied elsewhere.

What unlisted actually means

Unlisted removes an action from public discovery. It is useful for a casual group where forwarding is acceptable and the content is not sensitive. It does not require a secret password or prove the recipient’s identity. Treat the URL like a shareable invitation, not an encrypted document vault. If an unlisted link reaches the wrong audience, pause or close it while you assess the situation. Changing a status stops new responses but does not recall copies. Move future work into an appropriate private workspace and avoid reusing the old action for confidential material. A new link alone is not a complete security process.

Private workspace access

Create a workspace, invite the intended people and choose that workspace in the builder. Private actions use server-side membership checks. A member’s role determines whether they can view, respond or edit; membership is separate from a personal paid plan. The workspace owner’s licensed capacity applies to work created inside that workspace. Invite a person through the workspace invitation flow rather than relying on the action URL to grant access. Invitation links are expiring and recipient-bound. Removing membership prevents future authorized access but does not erase information that person previously saw. Review membership when a project ends or someone changes responsibilities.

Troubleshoot an access error

First check which account is signed in and whether it matches the invited address. Confirm that the invitation was accepted and that the action has actually been published and approved. A draft, paused, archived or pending action may remain unavailable even to someone who received its URL. Closed approved actions can show results while refusing new responses. Do not solve a private access problem by making the action public without reviewing its content and participants’ expectations. Ask the workspace owner to check membership and the action’s current status. Send support the URL and error without pasting private responses, invitation tokens or authentication cookies.

Continue with related help

Search the help center · Current plans and limits · Contact support

Still need a hand?

The site assistant can find related guides. For an account-specific issue, use the support form and include the page URL and exact error, without passwords or payment details.

Contact support ↗