Team and access
Mabel lets you give clients and teammates their own sign-in, without giving them your GitHub repository.
Roles
People belong to your account with one of three roles.
| Member | Admin | Owner | |
|---|---|---|---|
| See sites, forms and content | Yes | Yes | Yes |
| Read submissions, mark them handled or spam, mark all read | Yes | Yes | Yes |
| Edit posts, pages, data files and media | Yes | Yes | |
| Create and edit sites and forms | Yes | Yes | |
| Delete submissions | Yes | Yes | |
| Invite and manage people | Yes | Yes | |
| Delete sites and forms | Yes | ||
| Billing and account settings | Yes |
A client who only needs to read and handle form submissions can be a Member. A client who also edits their own content needs the Admin role.
Roles apply to the whole account, so a person can see every site on it. If you keep different clients’ sites on separate accounts, each client only sees their own.
Invite someone
- Open Invite member from your account.
- Enter their email address and choose a role.
- Send the invite.
They receive an email with a link. They sign in, or create an account with the same email address, then accept the invitation. You can resend or cancel a pending invitation at any time, and the person can decline it.
Invitations are tied to the email address. If someone signs in with a different address, they cannot accept it.
Editor limits
Everyone on an account counts as an editor. The number of people you can have is the total of the editor allowance of each of your sites, so it grows as you add sites and move them to paid plans:
- Free: 3 editors
- Pro: 5 editors
- Power: 25 editors
An account always has at least the allowance of one Free site, so you can set things up before adding a client. When you reach your allowance you are asked to upgrade a site before inviting more people.
Removing access
An Owner can remove a person from the account. People can also remove themselves. Removing someone stops them signing in to your sites, and does not change anything in your repository.