One Table or One per Client: How Should You Structure It?

Deciding between one table or one per client is a question service providers face early. One table with permissions is usually right; a table per client is right in specific circumstances.

What each approach costs

Neither is free, and the costs appear at different times.

One table means permissions must be configured correctly from the start
Separate tables mean the same structure maintained many times
One table makes cross-client reporting trivial
Separate tables make accidental data exposure structurally impossible

When each fits

Approach	Fits when
One table, client field	Same process for everyone, cross-client reporting needed
Table per client	Processes differ materially, or isolation is contractual
Duplicated template	New clients onboarded onto a proven structure

How to implement either in Jestor

For one table, add a client field in Jestor and make it required.
Scope permissions so each client sees only records where they are the responsible party.
Build the central dashboard reading across all clients.
For separate tables, duplicate the structure — duplication copies fields and automations without records.
Organize each client's tables into their own folder.

Why choose Jestor for service provider structures?

Jestor applies permissions by role, field, and action, which is what makes one shared table safe — and duplication copies structure and automations without records, which is what makes the alternative maintainable.

Because duplication excludes records deliberately, setting up a new client from an existing structure carries no risk of another client's data travelling with it.

Frequently Asked Questions

Does duplicating a table bring the data?

No, only the structure, fields, and automations. See jestor.com.

Can one table keep clients separated?

Yes, through record-scoped permissions.

How do I report across clients?

From a central dashboard on the shared table.

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 and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,