Skip to contentWork

RaiseNow

User management

A permission model for every org size

Role
Product Designer · one of three
Year
2024 – 26

The problem

RaiseNow serves nonprofits at both ends of the scale: single-account clubs and multi-tenant NGOs running dozens of regional accounts. One permission model covered both, so some users were over-privileged and others locked out of work they were accountable for.

What I did

I designed the permission model and the three screens that manage it: the users table, the invite modal and the detail panel. Most of the work went into making a complex model easy to read and change.

Six roles

I interviewed enterprise customers and our customer success team to map how access was actually used. From that came six roles, each scoped per account. A Developer role came out of an interview rather than the brief (webhooks and API credentials, explicitly not refunds), and Finance Officer kept supporter data because support agents troubleshoot with it.

Permissions matrix: six roles across the columns, and rows for touchpoint solutions, donations and payments, payouts and settings, each marked allowed or not per role
The six-role matrix from the research: what each role can see and do, by area.

Role tags

Each role has its own colour and icon, so you can tell them apart at a glance. Roles are scoped per account, so hovering a tag opens a popover with the accounts it covers. Filtering works on the same tags: the chips above the table are the filter.

Filtering by two roles, then the accounts under Scarlett Holmes's Account Admin tag.

Invites

The invite modal works on the same model. Each role in the picker says what it covers, and every role is paired with an account. Several people can be invited in one go.

Inviting two people as Campaign Managers for Basel and Geneva.

Bulk edits

Tick two or more people and a floating bar offers to edit their roles and accounts or remove them together.

Two rows ticked in the users table, Thomas Beck and Scarlett Holmes, and a floating bar below them: 2 selected, Edit roles and accounts, Remove users.
Two Campaign Managers selected.

Changing access

A person's detail panel shows their roles and accounts as a summary. Change access turns it into an editor with one row per role and account, so one pairing can change without touching the rest.

Scarlett Holmes's access, from summary to editor and back.

Outcome

Six roles, validated across org sizes, implemented in the users table, the invite modal and the detail panel.