> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Run a Process With External Participants
- URL: https://blog.jestor.com/process-with-external-participants/
- Published: 2026-09-17T22:34:46.000Z
- Updated: 2026-09-17T22:34:46.000Z
- Author: Bruno Bannach

To run a **process with external participants**, you need two things: a way for them to contribute without an account, and a boundary that makes internal information genuinely unreachable.

## Where external collaboration goes wrong

The usual solutions are either too closed or too open.

- Everything handled by email, so nothing enters the process
- Accounts created for people who will use them twice
- Access granted broadly because scoping seemed complicated
- Internal notes visible to someone outside the company

## Three levels of external participation

| Level                   | Mechanism                       | Account needed |
| ----------------------- | ------------------------------- | -------------- |
| **Submit once**         | A public form                   | No             |
| **Update their record** | An update link                  | No             |
| **Ongoing visibility**  | Scoped permissions and branding | Yes            |

## How to set it up in Jestor

1. Use a public form in **Jestor** for first contact — no account required.
2. Use an update link when you need someone to correct or complete an existing record.
3. For ongoing access, apply permissions by role, field, and action, scoped to their own records.
4. Hide internal fields at permission level rather than removing them from a view.
5. Apply **White Label** branding so the experience carries your identity, not a vendor's.

## Why choose Jestor for external collaboration?

**Jestor** applies the same Super Form engine to public links as to internal cards, so an external form can carry conditionals, connected records, and embedded content.

Because record scoping is a permission rather than a filter, an external participant cannot reach anyone else's data by changing what is displayed.

## Frequently Asked Questions

### Do external people need accounts?

Not for forms or update links. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### How do I hide internal fields?

At permission level, not by filtering a view.

### Can the experience carry our branding?

Yes, through White Label settings.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.