Skip to main content
FundWisr™

Getting started

Your team and what each role can see

Inviting people, the eleven roles, which ones use a seat, and how to give a consultant or auditor narrow access without handing over the organization.

2 min read
On this page

Inviting somebody

  1. Open Settings, then Team.

  2. Enter their email address and choose a role.

  3. Send the invitation.

    They get an email with a link. Opening it puts them in your workspace with the role you chose. Invitations expire, so send it when they are ready to accept it.

The eleven roles

RoleWhat they can do
OwnerEverything, including billing and granting permissions. Derived from who created the workspace.
Board PresidentReads everything, writes governance, can invite people and grant access. No billing.
Board MemberReads governance, finance dashboards, programs, and generated documents.
Board Member (portal only)Their own documents, disclosures, and meetings. Uses no seat.
Staff Admin / COOWrites to every part of the platform that runs the organization and can invite staff. No billing.
FinanceFinance, budgets, and revenue read and write. Reads grant financial reporting.
DevelopmentRevenue, community, grants, and funding corridors, read and write.
Program StaffPrograms, their own assigned actions, and evidence uploads.
VolunteerThe volunteer portal only. No access to the main workspace.
Consultant / ExternalNothing by default. Granted to named tools or documents, time-limited.
Auditor / FunderRead-only, and only what is specifically shared. Time-limited.

The two that catch people out

Board Member versus Board Member (portal only)
Board Member is real access to the workspace and uses a seat. Board Member (portal only) is the ordinary trustee: they sign their conflict disclosure, read their packet, see their meetings, and never enter the workspace. Most of your board should be portal only.
Consultant and Auditor start at nothing
Both roles begin with no access at all, and you grant specific tools or documents for a set period. This is deliberate. Somebody helping with a grant application does not need your donor list, and an auditor does not need your program participants.

Sensitive access

Some information is gated separately from the role: salary figures, and identifying details about the people your programs serve. A member can hold a role without holding sensitive access, and you grant it as a separate switch on their row.

Read next

Something here wrong, missing, or out of date? Email support@fundwisr.ai and tell us which chapter. Documentation defects are treated as defects.

FundWisr uses strictly necessary cookies to run the platform, plus optional categories you can choose. See the Cookie Notice for details.