Skip to guide
Brandlit
FIELD NOTE / 03 · 3 min

The right space for your people.

One shared team or separate private client spaces. You choose.

Inside this guide
03 / 01

Choose how records are shared

Personal apps keep saved data private to each visitor. Sign in with a verified Brandlit account to use your own saved data across devices. Guest data stays with that browser. Invited team apps use one shared document. Open People & data to review or enable the shared workspace; some team briefs enable it when the app is created.

Choose One shared workspace when everyone should see the same records. Choose Private client spaces when each invited account needs its own document. This choice is fixed for the app; create a separate app to use a different mode. Existing visitor data is never moved into client spaces.

03 / 02

Give every client their own space

In People & data, choose Private client spaces. Each invited, verified account sees only its own saved records. The app owner can use Open space or the selector above the live app to open any client document. The generated app cannot choose an account or open another client’s records.

Every space starts empty. Editors add and update their own records; viewers read; only the app owner can remove records or fields. Up to 100 client spaces are available over the lifetime of an app, including archived spaces. Removing a client ends their access but keeps their document available to the owner. Reinviting the same account reopens that account’s retained document.

Use Download data above a live app to keep a JSON copy of the current space. In App Studio, Files & backups lets the owner select a client space for a runnable export or checked recovery of its last 20 saved versions. Restoring one client does not change another client’s records.

03 / 03

Exchange briefs and deliverables

Open a hosted private client app and choose Files in the Brandlit header. Each client has a separate file room. The owner can choose another client using the space selector. Editors upload and download; viewers download; only the owner moves files to trash, restores them or permanently deletes them.

JPG, PNG, WebP, GIF, PDF and UTF-8 TXT, CSV and Markdown files are supported: up to 5 MB per file, 20 MB per client space, and 50 MB or 100 files across the app. Trash continues to count toward the allowance. Files remain in trash until the owner restores them or confirms permanent deletion.

Download space includes that space’s active files, current records and file review histories in a ZIP with a manifest and file hashes. This is an archive, not an automatic file restore. Ask the builder to attach a file to a project or record. Client apps can upload, open and download supported files inside the app. A file attached to a saved record must be detached before it can move to trash. App-source downloads with saved data include only files referenced by that selected space’s records. The downloaded copy keeps files locally in its browser; it does not sync with the hosted room. Importing that backup with data creates a new private copy with its attachments.

03 / 04

Keep the client’s decision with the file

In a client’s file room, the studio owner chooses View review on a file, adds a message and selects Request client review. The client must be an active editor. The request appears in their Files panel; it does not send an email.

The invited client opens the review, downloads the exact file, then chooses Approve this file or Request changes. A confirmation saves the decision. Changes require a note. The owner cannot approve on the client’s behalf, and viewers cannot submit decisions.

Each decision stays tied to the file’s content fingerprint and remains outside generated app code. Uploading a new file requires a new review. The owner can withdraw a pending request; moving its file to trash also withdraws it. Reinviting an account after its access changes requires a fresh request.

Download decision record saves the file details and review history. Up to 20 rounds are kept per file, with 400 characters per note. Permanent deletion removes both the file and its review history, so download any record you need first. These are product review decisions, not legal electronic signatures.

03 / 05

Invite the right people

Create an invitation for a person’s email address. They sign in with a verified Brandlit account using that address to accept the single-use invitation. An app can have up to 100 members.

Choose Editor for someone who adds and updates records, or Viewer for read-only access. Editors cannot remove records or fields. The owner controls membership and access.

03 / 06

Change access as the team changes

The owner can pause and resume invited access or revoke a member’s permission. Every save rechecks membership and the current document version. Live updates respect unsaved form inputs.

Publishing an invited team app does not make its shared records open to every visitor. Members still need the account and permission required by that workspace.

03 / 07

Understand a downloaded copy

A downloaded app uses local storage on the device where it runs. It does not keep synchronizing with the hosted team. An imported backup starts as a new private project with no inherited members or invitations.