Step 4 · Invite your team

Add the people who write or review the content. Users are unlimited on every site.

Roles

• Owners and admins see Overview, Content, Visibility, Assistants and Settings (Settings holds Team, Deploy, Keys and Integrations). Editors, authors and viewers see Overview, Content and Assistants; Model, Visibility and Settings are only for owners and admins, and opening them by URL redirects to Overview.
• Assistants is where anyone on the site connects their own ChatGPT, Claude or other assistant over MCP, and disconnects the ones they connected.
• A person can have different roles on different sites.
• An agent connected by a person can never do more than that person, with their current role. If their role is lowered or they are removed from the site, their agent loses the same right away. See What the agent can do.

Invite

1. In your site, go to Settings → Team → Invite. Enter the email and the role.
2. Pluma creates a single-use link, valid for 7 days, and shows it to you to copy. Send it however you like (email, WhatsApp). Automatic sending by email comes once the email service is connected.
3. The person opens the link:
   • If they don't have an account, they create it right there with that email.
   • If they already have one, they sign in and accept.
4. They show up in Settings → Team with their role. Pending invitations can be revoked.

The link only works for the email you invited.

Change roles and remove people

• Owners and admins change roles and remove people.
• Only an owner can make someone else an owner or change an owner.
• A site is never left without an owner: the last one can't be removed or demoted.

Limit what someone can edit

An editor, author or viewer can be limited to part of the site: in Settings → Team, open their Access and pick

• content types they can create and edit (only Events and Blog posts), and/or
• single entries they can edit (only the Admissions page).

Leave everything unchecked for the whole site. Owners and admins always cover the whole site.

• Outside their access they can look at entries in the dashboard, but not change them. Their assistant only sees what's published there, like the public site.
• It never adds to their role: an author limited to Events still can't publish.
• Their agents get the same limit, at once: in the API, the MCP and a batch, a change outside it gives key_cannot saying what they can change.

Delete a site

Only an owner can. At the bottom of the site's home page, open Delete this site and type the site's name.

It deletes all of its content, files, keys, agents and deploy hooks, and removes everyone's access. There is no undo, so export it first if you want a copy.

Delete your account

In Account (top bar), open Delete your account and enter your password.

• Your name and email are erased, and you're signed out everywhere.
• The assistants you connected lose access right away.
• What you did stays in each site's history as "Deleted user".
• If you own a site, delete it or make someone else the owner first.

Signing in

You stay signed in on each browser until you sign out, or until you don't use Pluma there for 30 days. After that you sign in again, and Pluma deletes that sign-in (with the IP and browser name it kept) the next day.

Step 4 of the checklist

It checks itself off when someone accepts an invitation. If you work alone, click "Just me for now" in Team and the step is done.