# Workflow Visibility & Sharing

> Manage workflow privacy, share workflows publicly, and handle access requests in Glow.

A new workflow is visible to your whole team. Its author can narrow that to themselves or widen it to anyone holding the link.

## Visibility states

Open **Share** on the canvas and pick one of three levels under **Who has access**.

![The Who has access options: Private, described as Me only; Team, described as Everyone in team and currently selected; and Public, described as Visible for everyone with the link.](/images/docs/workspace/workflow-visibility-options.webp)
*Three levels, set per workflow. Team is where a new workflow starts.*

| Level       | Who can open it                         |
| ----------- | --------------------------------------- |
| **Private** | Only you                                |
| **Team**    | Everyone in the workspace (the default) |
| **Public**  | Anyone with the link                    |

**Private is genuinely private.** It hides the workflow from your own teammates, not just from outsiders. Use it for something half-built you would rather nobody adopted yet.

**Public gives read-only access.** Anyone with the link sees the steps, how they connect, and the shape of the logic.

> **A visitor sees the shape, not the contents.** Step names, the app each one
> belongs to, how they connect, and any sticky notes you left. Not the fields
> inside a step, not connected accounts, not variables or secrets, not run
> history. The one thing worth reading before you send a link is your sticky
> notes and step names, since those travel with the workflow.

The same panel carries **Publish to marketplace**, which is a different thing. It offers the workflow as a [template](/getting-started/templates/sharing-and-templates) others can copy, rather than a link to view this one.

## The public viewer experience

When a workflow is set to Public, external users opening the link see the **Public Workflow Viewer**.

They get the shape of the workflow, not its contents. They can move around the canvas and zoom, and they see each step's name, icon and number, plus the lines between them. What they cannot do is open a step: nothing a step was configured with is sent to a visitor at all.

- **Nothing can be edited.** No adding steps, no deleting them, no altering settings.
- **Step configuration never leaves your workspace.** A visitor does not receive the fields inside a step, the values you mapped into them, or the account it signs in with.
- **Run history is not shown.** Visitors see the workflow, never what it has processed.

The button at the bottom of the view depends on who is looking. Someone without a Glow account sees **Sign up for free**. A shared workflow doubles as a way in for the person you sent it to. Someone already signed in to Glow sees **Request access** instead, which asks to join your workspace. Worth knowing before you post a link somewhere public.

## Asking for Access

**Request access** appears on a **Public** workflow, to someone who is signed in to Glow but is not in your workspace. It asks to join the workspace rather than to see that one workflow, and there is no message box to fill in. Your admins see who asked and which workflow they were looking at.

If an admin approves, the person joins your workspace as a Member. There is no view-only guest role, and roles do not vary by plan. Everyone in a workspace can open and edit the workflows in it. Approving a request is a decision about the whole workspace, not about one canvas. If you want somebody to see a workflow without joining, send them a Public link and leave it there.

A **Private** or **Team** workflow offers an outsider nothing to ask with. The link behaves as though the workflow does not exist, which is deliberate: someone who guesses a URL learns nothing about what you have built.

## What's Next?

- See how account security, workspace roles, workflow visibility and delegation fit together in [Permissions and Access](/manage/workspace-settings/permissions-and-access).
- Manage members and workspace roles in [Team Management](/manage/workspace-settings/team-management).
- Package a workflow for reuse instead of sharing a link in [Publishing and Forking](/getting-started/templates/sharing-and-templates).