Platform Features
Team members, roles & area permissions
Team members, roles & area permissions
The Team page lets you give trusted people access to your organization portal, each scoped to only what their role needs. The website is the multi-user surface — one org can have several portal users at different levels.
What it's for
Delegating the portal safely: a bookkeeper who only touches finances, a volunteer who only writes posts, a board member who only reads. Grant the narrowest access that lets someone do their job.
How it works
Invite by email. The person must already have a Xerish account with that email. Pick a role, then Add Member.
Roles set sensible defaults:
- Admin — full access.
- Finance admin / Accountant — the Financial Center (payouts, reports, stewardship).
- Post author — content (posts, Funds, Discover).
- Media manager — content plus the public profile.
- Read only — view across surfaces, no operating.
Fine-tune per area. Open Permissions on a member to set each of ten areas — Inbox & Dashboard, Posts & Campaigns, Funds, Discover, Profile, Family Center, Followers, Analytics, Financial Center, Settings & Team — to one of three levels:
- Full — sees the area and may operate it.
- View-only — sees the area, read-only.
- Hidden — the area's menu entries disappear for that member.
Switching the preset re-derives every area from that role's defaults; only the areas you change from the preset are stored as overrides.
Governing limitations
- Owner is the single top authority — always Full on every area, can't be removed or edited here.
- Only the owner or an admin can add, remove or re-permission members.
- Today, database write paths still gate on the owner, so non-owner roles are effectively read-only at the data layer until that repoint ships. The role model currently governs server-action authorization and what each member sees in the menu.
- View-only is enforced at the navigation level today; page-level read-only enforcement is a follow-up.
Good to know
- Use Hidden to remove an area a member never needs — it's cleaner than leaving an empty page in their menu.
- A removed member loses portal access immediately; their giving history is unaffected.