A: Hey Rafael,

Here's how access control works:

Your processes are private by default. Nobody can see or access your processes, dashboard, or any of your data unless they're signed in to your team.

There are only two ways something becomes accessible to people outside your team:

Publishing a process — When you publish a process, it gets a "run link" (/run/...) that others can use to start a new instance of that process. This is by design, it's how you share workflows with clients, customers, or external collaborators. Unpublished processes are completely private.
Sharing a process instance — Individual running instances can be shared via a toggle, giving someone a direct link to view and interact with that specific instance. This is off by default for signed-in users.

Important: Even if a process is published, nobody can access your original process template to edit or modify it, they can only run a copy of it. Your original is always safe.

Run Link Access control — In your process settings, you'll see a "Run Link Access" option where you can choose between:
Anyone with the link (default, current behavior)
Team members only (requires sign-in and team membership to start the process)

This gives you full control over who can use your run links.