> ## 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 Give Clients Access to Their Own Data
- URL: https://blog.jestor.com/give-clients-access-to-own-data/
- Published: 2026-09-17T22:34:17.000Z
- Updated: 2026-09-17T22:34:17.000Z
- Author: Bruno Bannach

To **give clients access to their own data**, the scoping has to be a permission rather than a filter. A filtered view can be changed by the person looking at it; a permission cannot.

## What is at stake

Getting this wrong exposes one client's information to another.

- A filtered view assumed to restrict access
- Data reachable through another view of the same table
- Access reviewed by inspecting dashboards rather than permissions
- Sharing granted broadly to avoid repeated requests

## What a client-facing setup needs

| Requirement        | How to meet it                                                |
| ------------------ | ------------------------------------------------------------- |
| **Record scoping** | Permissions limiting them to records where they are the party |
| **Field scoping**  | Internal fields hidden, not just unfiltered                   |
| **Action scoping** | Read where they should not edit                               |
| **Branding**       | A custom domain and login page                                |
| **Submission**     | Public forms and update links, for people without accounts    |

## How to set it up in Jestor

1. Apply permissions in **Jestor** by role, field, and action for the client role.
2. Scope records so each client reaches only those where they are the responsible party.
3. Hide internal fields at permission level rather than removing them from a view.
4. Apply **White Label** branding — custom domain, login page, logo, and menu.
5. Use public forms and update links where the person has no account at all.

## Why choose Jestor for client-facing access?

**Jestor** applies permissions by role, field, and action, which is what allows one process to serve your internal team and your clients with entirely different visibility.

Because record-level scoping is a permission rather than a filter, a client cannot reach another's data by changing what is displayed.

## Frequently Asked Questions

### Can a filter be used to separate clients?

No — a filter can be changed by the user. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can clients submit without an account?

Yes, through public forms and update links.

### Will they see our branding or the vendor's?

Yours, with a custom domain and 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.