# Users & Permissions

Canonical: https://useformwork.com/docs/platform/users-permissions

Invite account members and understand the Admin and Standard roles.

Membership and roles apply to the whole account. FormWork currently has two roles: **Admin** and **Standard**.

## Role summary

| Capability | Admin | Standard |
|------------|:-----:|:--------:|
| Work with projects, forms, entries, tables, templates, and extensions | Yes | Yes |
| View account members and API keys | Yes | Yes |
| Create and revoke account API keys | Yes | Yes |
| Change the account name | Yes | Yes |
| Delete a form | Yes | No |
| Open Stripe checkout or the billing portal | Yes | No |
| Invite, remove, or change members | Available in Account Settings | Available in Account Settings |

The product currently enforces Admin specifically for form deletion and Stripe billing actions. Most day-to-day building and data operations are account-scoped rather than role-limited.

> Roles are not project-specific. A Standard user can work across the account's projects.

## Add a member

1. Open **Account Settings**.
2. In **Team Members**, select **Invite User**.
3. Enter the person's email address.
4. Choose **Admin** or **Standard**.
5. Select **Send Invitation**.

At present, the email must already belong to a FormWork user. The operation adds that existing user to the account; there is no pending invitation list, resend action, or emailed acceptance flow yet.

Promoting or inviting an Admin is a metered write and requires the account billing status to be active or trialling.

## Change a role

1. Find the member in **Team Members**.
2. Select **Edit Role**.
3. Choose **Admin** or **Standard**.
4. Select **Update Role**.

An account must retain at least one Admin. FormWork prevents removing or demoting the final Admin.

## Remove a member

Select **Remove** beside the member and confirm. Removing access does not delete forms, entries, templates, or other resources they created.

## Choosing a role

Use **Standard** for most builders and operations staff. Use **Admin** when someone must manage the Stripe subscription or delete forms. Because other account-management operations are currently broadly available, do not treat Standard as a read-only or restricted-data role.

If two groups must not see or edit one another's resources, place them in separate accounts rather than separate projects.

## Sign-in and user settings

FormWork currently supports email-and-password sign-up and login. A signed-in user can open **User Settings** to change their password by entering:

- Current password
- New password of at least eight characters
- New password confirmation

There are no Google/GitHub login buttons, per-device session manager, or admin session revocation controls in the current interface.

## Security habits

- Remove account access promptly when somebody leaves a team.
- Keep at least two trusted Admins where operationally appropriate.
- Give service integrations distinct [API keys](/docs/platform/api-keys), not a person's session.
- Use separate accounts for clients or teams that require data isolation.
- Review API keys as well as members during access reviews.