For client portals
Open the right window into your business.
Design a client portal on your actual project data, with row and field rules that define exactly what each invited client may see.
| Company | Owner | Stage | Value |
|---|---|---|---|
| 1Northstar | SSam | In progress | €18,000 |
| 2Fieldwork | AAlex | In review | €24,500 |
| 3Orbit Studio | SSam | Won | €12,000 |
| 4Common Ground | AAlex | In progress | €32,000 |
Give the work a relational home
Start with connected tables. A shared name in two spreadsheets is not a relationship.
- Clients
- Use a clear client relationship as the basis of access rules.
- Work
- Link projects or requests to the client that owns them.
- Updates
- Keep progress records related to the work they describe.
Decide who sees what, before the first screen
Groups grant access per table, row, field and action. Every surface follows those rules.
- Client identity
- An invited user belongs to one suite directory and the groups the builder assigns.
- Rows
- Limit access to work related to that client's records.
- Fields
- Omit internal notes and commercial details from both the screen and the API.
Different jobs deserve different screens
The Data grid is the starting point. Interface ideas can be described to the assistant and built over the same authorized data.
- Client home
- A dashboard built from the projects available to the viewer.
- Request form
- A focused interface for the records a client is permitted to create.
- Project detail
- A page showing authorized updates for one project.
Try this as your app brief
“Design a client portal for Projects and Updates. Clients read only their own projects. They can create requests, but cannot edit delivery status or read internal notes.”
This is an app design example, not a ready-made template. gtable is a work in progress and not open yet. Explore the product or other use cases.