TH SeedWebs
Documentation

Users and permissions

The four admin roles, exactly what each one can do, how to add someone to your site, and the limits of the Writer role.

Last updated 2026-11-18

A SeedWebs site can have many users. Each one is given a single role, and that role decides which menus they see in the admin panel, what they can edit, and whether they can publish.

Users are managed at Settings → Users (/admin/settings/users), which is open to Super Admin and Admin only. Other roles do not see Users in the Settings menu, and typing the URL directly gives “Not available for your role”.

The four roles

There are four: Super Admin, Admin, Editor, Writer. (The admin panel starts in Thai, where they appear as ผู้ดูแลสูงสุด, ผู้ดูแล, ผู้แก้ไข, ผู้เขียน.)

RoleWho it is for
Super AdminThe site owner. Everything, including resetting the site and restoring backups
AdminA trusted manager. Almost everything, except reset/restore and granting Super Admin
EditorRuns the content. Edits and publishes anyone’s work, but cannot touch site settings
WriterWrites for review. Sees and edits only their own work, and cannot publish it

The site owner’s email — whoever ordered the site — is made Super Admin automatically at creation.

The permission table

The admin panel hides buttons by role, and the API checks every request too, so calling the API directly is refused just the same.

TaskSuper AdminAdminEditorWriter
Dashboard✓✓✓✓
See content listsAllAllAllOwn only
Create content✓✓✓✓ (saved as Draft)
Edit somebody else’s content✓✓✓–
Publish✓✓✓–
Move content to Trash✓✓✓Own unpublished work only
Delete permanently from Trash✓✓––
Bulk actions on several items✓✓––
Create a translation✓✓✓–
Media: upload✓✓✓✓
Media: edit / move to trash✓✓✓Files they uploaded (not older or imported ones: no uploader on record)
Media: restore from trash✓✓✓–
Media: delete permanently / Empty Trash✓✓––
Members, Subscribers, newsletter send logs: view✓✓✓–
Store → Orders, Coupons: view✓✓✓–
Store → Coupons: create, edit, delete✓✓––
Authors, Staffs, Members (create/edit)✓✓✓–
Authors, Staffs, Members (delete)✓✓––
Forms (create/edit/delete)✓✓––
Form entries: import from a CSV✓✓––
Tour bookings: view and change status✓✓✓–
Tour bookings: refund through the gateway✓✓––
Settings → General, Site status, Code, Themes, Menus, Banners, Cookies, Chat Buttons, Marketing✓✓––
Settings → Payments, Store → Settings → Payments✓✓Can open, cannot save–
Settings → Users✓✓––
SEO (/admin/seo)✓✓––
Tools → Redirects, Import, Demos, API Tokens, Connected Apps, Backup✓✓––
Tools → Backup: restore from a snapshot✓–––
Tools → Reset (wipe the site’s content)✓–––
Logs → Activity, Email, Conversations✓✓––
Approve an AI app’s Publish request (whoever may make that change in the admin)✓✓Content changes– (declines their own)

The table says which role may do something; whether a row exists on your site also depends on plan and flags: Staffs, Members, Tours (with its bookings screen) and Donations need the team to enable experimental features, Members also the Business plan (or the trial), and Tours comes with no plan. See Admin panel overview; Donations’ roles are in Donations.

Things that catch people out:

  • An Editor sees one Settings item: Payments, the gateways the shop checkout and tour bookings share, under the bookings permission. The rest are hidden; saving needs Admin or above.
  • A Writer sees no Settings or Logs, and under Tools only Publish requests and Edit Shortcut; Edit Shortcut opens for Admin or above only.
  • Under Logs, Conversations appears once the site has an AI API key and the AI chat is switched on. Until then an Admin sees only Activity and Email.
  • Tour bookings are permissioned separately from tour content on purpose: a Writer who writes the tour pages does not see a customer’s name, email or phone number.
  • Likewise a Writer sees no Members, Subscribers or newsletter send logs (they list people’s names and emails; the newsletters themselves stay open), and no Orders or Coupons under Store (buyers’ details; a code anyone can spend). Products stay open.
  • Bulk actions work for Super Admin and Admin only. An Editor still sees the bar, but using it returns “Insufficient permissions”. A Writer never sees it.

A Writer’s “own only” restriction applies to Posts, Pages, Docs, Events, Products, Sliders, Books and Tours. It is matched on the email recorded when the item was created.

What a Writer can and cannot do

The Writer role follows WordPress’s Contributor model: write, submit for review, but never put it on the site yourself. What to know before handing the role out:

They see only their own work

Lists like Posts show only items that Writer created; opening someone else’s by URL reports not found (Post not found), not forbidden. Trying to edit or delete somebody else’s item by another route returns You can only modify items you created.

They cannot publish, and a publish request becomes a Draft

In the editor the status buttons offer Draft only.

The server checks again: a Writer’s save with status Published is saved as a Draft, with no warning. The screen says saved successfully. If a Writer reports “I saved it but it is not on the site”, this is the first thing to check.

The statuses a Writer can actually set are Draft and Trash.

Once published, they cannot save over it

After an Editor or Admin publishes the item, the Writer who wrote it can no longer save over it. The reply is:

This post has already been published — ask an editor to revert it to draft first.

They can still read it. To edit, an Editor has to set it back to Draft. On a page or post the Writer can Save without publishing instead, for an Editor or Admin to publish (Pages and posts).

The byline is locked to them

In the Post form, a Writer’s Author field is set to the Author linked to their account and cannot be changed, and the Co-authors section is not shown. A request from a Writer account that tries to change author_id or add co-authors has those values ignored; the rest of the save goes through.

If the account has no Author linked yet, creating a Post fails with a message saying an administrator has to create one first.

What a Writer can still do

  • Upload files in Media, and edit or trash the files they uploaded themselves — not older or imported files, which have no uploader on record (an Editor can change those); no restoring or deleting permanently
  • Edit their own profile at /admin/profile (name, phone) and add their own passkeys
  • Move their own unpublished work to the trash, with the trash button in the editor

Users and Authors are linked by email

Every new user gets an Author row created automatically, matched 1:1 by email, because the byline on your public site comes from the Authors table, not the user account.

  • These automatic Authors appear under Authors (/admin/authors) and are always created in the en locale. For a Thai name, add a translation there.
  • Editing an Author’s Display Name changes the byline readers see. Editing the name under Users changes the admin account’s own details.
  • An Author missing at first sign-in is created when the account loads.
  • An Author with no email is a guest writer who does not use the admin panel.

Email cannot change after the account is created

On Edit User the Email field is disabled, with the note “Email is the account’s identity and can’t be changed. A user migration feature is planned for a future release.” A new email sent through the API is silently dropped.

Email is the sign-in identity and the link to the account’s Author. To change someone’s email, create a new user with the new one and delete the old account: their content stays, but “own only” follows the old email, so a Writer no longer sees their earlier work.

Adding somebody to your site

You need Super Admin or Admin.

  1. Go to Settings → Users (/admin/settings/users).
  2. Press Add User.
  3. Fill in First Name, Last Name, Email (required) and Phone.
  4. Choose a Role. The default is Writer.
  5. Press Add User to save.

Worth knowing:

  • No invitation email is sent. Adding a user only grants that email access; tell them yourself to sign in at /admin/ with it.
  • The email has to match the one they sign in with. For Google, it must be that Google account’s address.
  • Duplicate emails are refused: “A user with this email already exists.”
  • An Admin cannot make anyone Super Admin. The option is not in the list, and a request through the API is refused with “Only a super admin can grant the super admin role.”
  • No plan limits the number of users. See Plans and billing for what plans do limit.
  • A token cannot manage users. Adding, changing or removing users, and disconnecting Tools → Connected Apps, need a signed-in person (session_required).
  • A token cannot change payment secrets. Setting, changing or clearing the Stripe secret key or webhook secret, or the Beam API key or webhook HMAC key (Settings → Payments), needs a signed-in person too (session_required), and so does the Connect button for Stripe, which creates a new webhook secret. A token marked Publishes without confirmation may still change the rest of the payment settings.
  • A token cannot publish by itself. Unless an admin marked it Publishes without confirmation, a change visitors would see is a Publish request over MCP and 403 confirmation_required over REST, as are a newsletter send and POST /api/email/send. An address any token adds to Subscribers waits as Pending. See Connect an AI assistant.

Ways to sign in

The sign-in page is at {site}.seedwebs.app/admin/, with three options.

MethodHow it works
Sign in with GooglePress the button and pick the Google account whose email an administrator added
EmailEnter your email and SeedWebs sends a 6-digit code. Codes expire after 10 minutes
PasskeyEnter your email and confirm with Face ID / fingerprint / device PIN. A passkey has to be added first, from /admin/profile

Common situations:

  • An email not yet on the Users page gets “You are not authorized. Contact your admin.” from Google sign-in.
  • Requesting an email code for an address that is not on this site moves on to the code field as usual, but no email is actually sent. That is deliberate, so an outsider cannot probe for administrator addresses.
  • Email codes are limited to 3 sent per hour per address, and 5 wrong attempts per code. A code that could not be sent is not counted.
  • A session lasts about 2 hours. After that, sign in again.
  • You can add several passkeys per account (a phone and a laptop, say), managed under Passkeys at /admin/profile.

Changing roles and removing users

At Settings → Users, press Edit on their row (/admin/settings/users/{id}). Only First Name, Last Name, Phone and Role can be changed.

  • Granting Super Admin can be done only by somebody who is already Super Admin.
  • Editing or deleting another Super Admin is for Super Admins only. An Admin is refused with “Only a super admin can modify a super admin user.” (or “Only a super admin can delete a super admin user.” when deleting).
  • The last Super Admin is locked. With only one active Super Admin left, the Role field is disabled, Delete disappears, and a note asks you to promote somebody else first, so a site cannot lock itself out of its own admin panel.
  • Deleting a user cannot be undone. You are asked to confirm once. Their content and Author row stay, so public bylines do not disappear.
  • Sessions and API tokens follow. A lower role, or removal (deleting them, or inactive or suspended via the API), hits their next change and token use at once and pages they only view within a minute; removal also revokes tokens. A higher role: at next sign-in. Exception: for someone deleted or deactivated before November 2026, old tokens still show Active and work again once they return, so revoke those on Tools → API Tokens first.
  • Who did what — Logs → Activity (/admin/logs/activity) records the email and name behind every create, edit and delete. Admin and above.
  • Tools → Reset (/admin/tools/reset, Super Admin only) wipes the site’s content and deletes every user who is not a Super Admin. You have to add people back afterwards.
  • SeedWebs team accounts can enter your admin as Super Admin to help, and may appear in Users. A suspended one loses all access here within minutes.
  • A page blocked by your plan, or not enabled, says “is not included in your plan” or “is not enabled”, not a role message. If you are Super Admin and still cannot get in, check the plan and feature flags rather than permissions. (The permission message is “Not available for your role”.)
  • The whole sidebar is mapped in Admin panel overview, and working with content in Pages and posts.