Projects for clients

Group forms by client, decide who can see each group, and hand a finished project to the client without changing a single endpoint.

5 minWorks on every planUpdated Sep 22, 2026

Projects and workspaces

A project is a folder for forms inside your workspace, usually one per client or per website. Every form belongs to exactly one project, and access is granted per project: someone given a client's project sees that client's forms and submissions and nothing else.

	Project	Workspace
Plan and bill	Shares the workspace’s	Its own
Submission quota and seats	Shared	Its own
Who can see it	Owners, admins, and people you grant	Its own members
Use it for	Each client site you run	A client who pays for their own account

Every workspace has a default project where new forms land when you do not pick one. It cannot be archived, deleted or transferred, so there is always somewhere for a form to go.

1
Create a project
Open Projects and click New project. Name it after the client or site. Owners and admins can create projects; members and clients cannot.
2
Move forms into it
New forms can be created straight into the project. For an existing form, open its Settings and choose the project from the Project picker. The picker only appears once the workspace has more than one project.
The endpoint does not change. Moving a form keeps its public key, so a live site posting to it carries on without a redeploy. What changes is who can reach it: access follows the project.

Give people access

Open the project, then its settings. Who can reach lists everyone in the workspace. Owners and admins show Full access because their reach is the whole workspace. For everyone else, pick an access level:

Access	What it allows
No access	The project, its forms and its submissions are invisible to them.
Viewer	Reads and exports submissions, and sees how a form is set up. Changes nothing.
Editor	Create and configure forms, and act on submissions.

Someone with the client workspace role is always capped at Viewer, whatever this picker says. To bring in someone new, invite them from Team and tick the projects they should see.

Hand a project to a client

When a client takes over their own account, transfer the project to their workspace. The project, every form in it and all their submissions move together, and every endpoint URL stays exactly as it is, so nothing on the live site needs redeploying. Project transfer is part of the Pro and Agency plans.

Only a workspace owner can transfer, and only into a workspace they also own. The usual route: the client creates a workspace, adds you as an owner, and you transfer into it from the Transfer panel in the project's settings.
Recipients, spam rules, webhooks and integrations move with the forms.
Every per-project grant is removed, so nobody from your workspace keeps access unless they own the destination. The new owner can invite you back.
From the moment it moves, usage counts against the destination workspace's plan.

The default project cannot be transferred. Move the forms you want to hand over into a project of their own first.

Archive and delete

When an engagement ends, Archive project hides it from the sidebar and the project switcher. Its forms keep their endpoints and keep accepting submissions, so the client's site does not break. Reopen it any time.

A project can only be deleted once it is empty, including forms deleted recently that are still recoverable. Move or delete its forms first. Deleting a project never takes a live endpoint with it.

Next steps

Team membersInvite staff and clients, and choose what they can reach.Email notificationsSend each client’s submissions to the client.WebhooksProForward a client’s submissions to their own systems.