Users, Roles & Permissions

Remindax has three roles: Administrator (Owner) — the user who purchased the subscription, with full access; Administrator (Privileged) — full admin access without ownership; and Editor (Limited Access) — has only the capabilities granted on a per-user Permissions screen. Promotions use Make Admin / Remove Admin in the Users list; Editor scope is shaped one permission at a time.

The three roles

Role	What it is	Manage Users?	Access My Subscription?	Permissions model
Administrator (Owner)	The account owner who purchased the subscription	Yes	Yes	Full access
Administrator (Privileged)	Full admin access without ownership	Yes	Yes	Treated as master — full access across most areas
Editor (Limited Access)	Day-to-day operator	No	No	Granular — only what's enabled on their Permissions screen

Owner and Privileged Administrator both have admin-level access in most areas; the difference is that the Owner is the single billing-responsible user.

Editor permissions — how the model actually works

Editors don't have a fixed capability list. Each Editor's access is shaped by individual permissions an admin toggles on their Permissions screen. Common ones include:

Explorer / items

explorer_create — can create new reminders
explorer_update — can edit reminders
explorer_delete — can delete reminders

Contacts

contact_view — can see the contacts list
contact_create — can add contacts
contact_update — can edit contacts
contact_delete — can delete contacts

Settings

settings_view — can view settings; specific settings actions are gated further

Other areas — additional permissions exist for departments, document types, templates, drive, calendar, tasks, and reports.

This means two Editors at your company can have very different effective access. The answer to "What can an Editor do?" is always "whatever you've enabled on their Permissions screen."

Scope of an Editor's access

Editor capabilities are gated mainly by company and department scoping, not by item ownership. With explorer_update, an Editor can edit items in their scope — not only items they personally created.

What's reserved for the Owner or Privileged Administrator regardless

A few areas stay Owner/admin-only regardless of Editor permissions, including:

System Email Templates (the templates used for verification, password reset, etc.)
Developers / API credentials
Make Admin / Remove Admin on other users
My Subscription (plan, add-ons, billing, message credits)

What "Owner" means

The Owner is the user who purchased the subscription — distinct from a reminder recipient. The Owner is the single billing-responsible user.

Account ownership transfer is not currently supported in the product. If the Owner needs to hand the account to another person, contact support to discuss options.

Visibility columns in Manage → Users

Status — whether the user is active.
Verified — whether they've completed initial verification.
2SV — whether they've enabled two-step verification. 2SV is per-user opt-in via My Settings → Security; there is no admin "enforce 2SV for everyone" toggle. Admins can deactivate a user's 2SV from the user edit screen if needed (e.g. lost device recovery).
Actions — the row's ⋯ menu (Edit User, Make Admin / Remove Admin, Delete User).

Edge cases & gotchas

Don't lock yourself out. If you Remove Admin from yourself, ensure at least one other Administrator (or the Owner) remains.
Owner vs Privileged Administrator. Both have admin power; the Owner is the single billing-responsible user.
Contacts ≠ Users. Receiving reminders does not require a User account — and shouldn't, since Users consume seats. See Contacts vs Users.
No custom role builder. Editors are tuned via Permissions toggles, not by creating named custom roles.
Ownership transfer isn't available in the current product.