This article is part of our series on the platforms we build for nonprofits, with the Normandy Park Police Foundation (NPPF) as our working example. The series starts with why it's one platform. This one is about the piece that makes "one platform" possible: one account, and the roles that decide what it opens.
The account sprawl problem
On a typical small-nonprofit stack, a person who gives monthly, belongs to Blockwatch, and edits the newsletter has three accounts on three products, with three passwords and three permission models. The organization has no single picture of who that person is, and the person has no single place to manage anything.
Worse, the permission models don't match the organization. A newsletter product has "admin" and "author." A donation product has "admin" and "viewer." Neither has "Treasurer," "Blockwatch captain," or "grant volunteer," because those are roles in the Foundation, not features of a product.
Sign in without a password
Sign-in is by emailed link. A password is optional.
Signing in to the NPPF platform means entering an email address and opening the link that arrives, on the device and in the browser where you asked for it. Anyone who prefers a password can set one, but nobody has to. Once their email address is confirmed, a person can also add a passkey on their account page and sign in with Face ID, Touch ID, or their device's screen lock.
For a community organization this matters more than it sounds. The people signing in are neighbors, donors, and retirees, not an IT department. Forgotten passwords are a familiar chore on a volunteer-run site, and an emailed link or a passkey sidesteps most of them. Sign-in runs through a specialist provider, so the Foundation never sees anyone's password.
Every account starts equal
A new account opens its owner's own records and nothing else, and says whom to ask for more.
A new account has no special access. It opens its owner's gifts, plans, and choices, and the team's side of the site tells it plainly that it doesn't include the site tools. Access comes only from roles, and a role is something the Foundation gives, never something an account starts with.
How access is decided: roles, areas, and actions
This is role-based access control, and the idea is simple: access belongs to a role, and people hold roles. To change what one person can do, you change their roles. To change what a job can do, you change the role once, and it changes for everyone who holds it. Nobody's access is a one-off setting that someone has to remember.
On the NPPF platform, every decision comes from three things.
Roles, named for the Foundation's own org chart:
- Site roles: global administrator, site administrator, editor, contributor, and reporter.
- Blockwatch: a Blockwatch administrator, and the volunteer positions of province coordinator, captain, and block contact, plus the member role every confirmed neighbor holds.
- The board: the offices in the bylaws (President, Vice President, Secretary, Treasurer, Member at Large, and Director), and a board member role every board member holds.
- Volunteers and staff: grant volunteers and a store manager.
Areas, the parts of the work: News, Documents, Site content, Events, the Inbox, Email lists, Users and roles, the Activity log, Blockwatch, Donations, the Board room, Filings and dates, Grants, Expenses, Budget versus actual, and the Store. Which areas a role reaches is fixed in the platform itself. A Director reaches the Board room; a store manager reaches the Store and nothing else.
Actions, the four things a role may do in the areas it reaches: create, update, delete, and publish. These live in the sign-in service's role policy, where every role has a resource of its own holding its actions. Nothing is implied: update doesn't include publish, and create doesn't include delete. That's how a contributor can write and fix drafts while an editor decides what goes public.
Every request on the team's side is answered the same way, on the server, whatever the screen shows.
Here's the starting point we set up, in a few rows:
| Role | Reaches | Actions |
|---|---|---|
| Reporter | News, events | Create, update, publish |
| Contributor | News, documents, events | Create, update (an editor publishes) |
| Editor | News, documents, site content, events | All four |
| Province coordinator | Blockwatch, their own provinces | Create, update, delete |
| Block contact | Blockwatch, their own provinces | None: sees requests and members, confirms nobody |
| Director | Board room, filings and dates, grants, expenses, budget, events | Create |
| Secretary | The same as a Director | Create, update, delete (approves minutes) |
| Store manager | The Store | All four |
The split is deliberate. Which areas a role reaches is in the platform, so a slip in a settings screen can never open the Board room to the wrong person. Which actions a role holds is in the policy, so the board can widen or narrow a role without a developer and without a new release: give the Treasurer update in the Board room, and the site follows within a minute. If the platform can't read the policy at all, it refuses every team request rather than guess.
A few jobs belong to one office, and those are rules in the platform rather than actions. The Treasurer keeps the books and reviews everyone's expenses, and nobody approves an expense of their own. They're rules because an action applies in every area a role reaches: update for the Treasurer in Grants would also let them approve Board room minutes.
The role says what; the record says where
Some roles need a place as well as a job. A Blockwatch captain confirms neighbors, but only in the provinces they serve. A grant volunteer records expenses and time, but only on the grants they're named on. The role says what someone may do; the platform's own records say where.
Two halves, kept where each belongs. Neither one alone opens a province.
Appointing a volunteer records the position and the province together.
That's why Blockwatch positions are given on the Blockwatch desk rather than anywhere else: appointing someone writes the position to their account and records the province in the same step. A coordinator appoints captains and block contacts in their own provinces; the Blockwatch administrator and the site's administrators appoint anyone, anywhere. Removing a volunteer's last province removes the position too.
Grant volunteers work the same way. The Treasurer or a global administrator names them on a grant's own page, and each volunteer sees only those grants, and only their own entries on them.
The Blockwatch member role looks after itself. Nobody gives it by hand: it's added when a volunteer confirms that a neighbor lives in a province, and removed when they leave their last one. A member sees a province's volunteers and how it keeps in touch only while they hold the role and are confirmed in that province.
Who gives each role
Four ways in, one account. Each role is given where the decision behind it is made.
Users and roles lists every account with every role it holds, and filters by role.
Site roles, board offices, the board member role, the Blockwatch administrator, and the store manager are given by the Foundation's administrators. An invitation from Users and roles carries no role; the person signs in first, and their roles come after. Users and roles then shows every role each person holds, however many: one neighbor can be an editor, a captain, and a Director at once. An account holds at most one site role, one board office, and one Blockwatch position, with the member roles beside them.
The safeguards are the part an organization feels when something goes wrong:
- Roles go only to confirmed email addresses. The desks that appoint volunteers refuse an unconfirmed address, and Users and roles marks any account whose address isn't confirmed yet, with a button to remind the person.
- The board's room is the board's. Only board offices and the board member role open the Board room. An administrator who isn't on the board doesn't see it at all; one who is opens it through their office.
- Offices and board membership are separate. Someone joining the board gets both; when their term ends, both come off, unless the board wants them to keep the board member role.
- Nobody locks themselves, or anyone above them, out. Nobody deactivates their own account, and only a global administrator deactivates an account that holds an administrator role, a board office, or the board member role. Deactivating anyone signs them out everywhere at once, and their past work stays in the activity log.
A key on every page
The key beside a page title shows which of your roles open it and what each lets you do there.
None of this works if people have to guess what they're allowed to do. Beside every page title on the team's side is a key. It names the roles you hold that open that page, and for each action whether you have it and through which role. A role that opens a page but holds none of its actions shows as view only. The key links to your account page, which lists every role you hold and what it allows, area by area.
For the administrators, the Roles tab of Users and roles shows the whole policy as a table read live from the sign-in service: every role, the areas it reaches, and its four actions. If a role is missing or has no actions, it says so, because a role the policy doesn't define opens nothing.
Changes made on the site, from a published story to a confirmed neighbor to a deactivated account, are recorded in the activity log, and each person sees only the entries for the tools they can open.
What a member sees
From a free account, a person sees their own gifts with receipts and year-end statements, their store orders with theirs, their recurring gifts, their emergency preparedness progress, their Blockwatch membership or request, what any role they hold lets them do, their email choices, their passkeys, and their profile and photo. Gifts made before the account existed join it once the person confirms the same email address.
The preparedness plan deserves a mention. Someone who builds a household emergency plan is entering where their family meets, who to call, and what's in their kit. That plan is shown only to the account holder: no administrator screen shows it, and it's never sent to the email system or anyone else. A sensitive personal record can live on the Foundation's platform without anyone at the Foundation opening it there.
Privacy as a design constraint, not a page
The platform collects only what each feature needs. The Province Finder never saves or logs an address. A Blockwatch request (name, address, and any phone number and message) is shared with that province's volunteers, the Blockwatch administrator, and the site administrators, and its contact details are cleared if the person leaves. Contact form messages are deleted on request. Visitor statistics come from Google Analytics on public pages only. It sets cookies, knows a signed-in visitor only by a code (never a name or email address), and is never used for advertising or loaded in the admin, on sign-in pages, or when a browser sends Global Privacy Control. Corrections and deletion requests go through the privacy page.
None of that is a privacy policy written after the fact. It's what the system does, because we built it for an organization whose members are neighbors and whose trust is the program.
Why one account is the whole point
Every other article in this series describes a feature: giving, Blockwatch, publishing, the back office. One account with the organization's own roles is what makes them one platform instead of four products. It's also the thing you can't retrofit; it has to be the foundation. When officers change after an election, their access changes with their roles, the same day, with no passwords to hand over.
We offer this platform to other organizations, with roles that match your own org chart. See our platform for what's in it. If your organization is managing people across several products and nobody has the whole picture, a free assessment will tell you plainly what a single account model would and wouldn't change.
