# Accounts & Projects

Canonical: https://useformwork.com/docs/platform/accounts-projects

Organise FormWork resources and understand account-wide boundaries.

Accounts are the security and billing boundary. Projects keep related forms, tables, templates, and integrations together inside an account.

## At a glance

| Level | Contains | Scope |
|-------|----------|-------|
| Account | Users, billing, API keys, projects | Membership, roles, subscription, API authentication |
| Project | Forms, Data Tables, templates, extensions | Organisation and shared project resources |

Every account member can access its projects. FormWork does not currently support project-specific membership or permissions.

## Accounts

Signing up creates an account and makes you its first **Admin**. An account has a name and can have multiple members. A user may belong to more than one account.

Account Settings contains:

- **Account name**
- **Billing** status, plan, usage, and subscription actions
- **Team Members** and their Admin or Standard role
- **API Keys**

### Create another account

Use the account switcher and choose the option to create an account. Enter its name. The creator becomes an Admin of the new, separate account.

### Switch accounts

Use the account switcher in the main navigation. The selected account determines the projects, billing record, team, and API keys shown in the app.

## Projects

A project is a practical workspace for one client, business process, product, or department.

Each project has these tabs:

- **Forms** — public data collection, entries, views, imports, exports, and files
- **Data Tables** — structured records used in options, lookups, and workflows
- **Templates** — reusable content and layouts for email and PDF steps
- **Extensions** — built-in extensions and API Connectors

### Create a project

1. From the dashboard, select **Create Project**.
2. Enter **Project Name**.
3. Optionally add a **Description**.
4. Select **Create Project**.

Project creation requires active or trialling billing. Plan usage records the number of projects, but current plan overages are informational rather than automatically blocked.

### Edit a project

Open the project settings/edit action, change **Project Name** or **Description**, then select **Save Changes**.

### Delete a project

Select **Delete Project** and confirm the browser prompt.

> Deleting a project removes its forms, entries, Data Tables, templates, and extension configuration from active use. The interface treats this as irreversible, so export anything you need first.

## How to organise projects

Use a new project when resources should be navigated and managed as a distinct body of work—for example **Supplier Onboarding**, **Customer Support**, or a named client.

Keep resources together when they need to share:

- Dynamic option tables
- Cross-form references
- Reusable email or PDF templates
- The same API Connector environments

Because access is account-wide, creating separate projects does not isolate one team from another. Use separate accounts when you need a true membership or billing boundary.

## Resource ownership

Moving resources between projects is not currently an admin operation. Choose the project before creating a form, table, template, or connector. To recreate a designed solution in another account, a supported starter-project link may instantiate a prepared project during sign-up or account selection.

## Related guides

- [Users & Permissions](/docs/platform/users-permissions)
- [Plans & Billing](/docs/platform/billing)
- [Data Tables](/docs/data-tables/overview)
- [Reusable Templates](/docs/templates/overview)
- [Extensions & Integrations](/docs/extensions/overview)