Running Plainpad for a Small Team

Running Plainpad for a Small Team

Plainpad supports multiple users on one instance. It is worth being precise about what that means, because “multi-user” gets used to describe everything from shared documents to real-time collaborative editing, and Plainpad is neither.

What multi-user actually means here

Each user has their own account and their own notes. An administrator manages accounts and application settings. Notes are private to the user who owns them.

There is no shared note, no comment thread, no presence indicator, no “Alex is typing”. If two people need to edit the same paragraph at the same time, this is the wrong tool and we would rather say so.

What it is good for: a team, a family or a small company that wants one instance, one backup, one update to apply, with everyone’s notes kept separate.

Setting it up

  1. Install Plainpad and log in with the default administrator account that setup creates - change its email and password straight away.
  2. There is no self-registration: only an administrator can create accounts, so a team instance is closed by default.
  3. Create an account per person and hand over the credentials out of band.
  4. Ask everyone to change their password on first login.

That is genuinely the whole process. Ten minutes for a team of five.

Roles, briefly

Roles decide what a user can reach beyond their own notes - the administrative areas, the settings, the user list. Give the administrator role to the person who will apply updates and restore backups, and nobody else. A regular account cannot reach the settings that would break the instance for everyone.

The same model applies to the REST API. A limited account is limited through the API too.

What a team should agree on

Since notes are private, the team conventions that matter are about what goes where, not about permissions:

A shared naming prefix helps even without shared notes. If everyone titles meeting notes 2026-10-19 - standup, then comparing two people’s version of the same meeting is a copy-paste rather than an archaeology project.

One instance, one set of chores

The real argument for a shared instance is operational. Five separate installs means five backup jobs, five update cycles and five certificates to renew. One install means one of each, and the per-user separation is handled by the application rather than by you.

Services

Want a hand with Plainpad?

We can host it for you, help you fix a problem, put your brand on it, build something new or move your notes over.

See our services