Permissions matrix

GreekManage has five role tiers stacked from broadest to narrowest scope: Platform admin (cross-organization, GreekManage operators), National admin (an entire organization), Regional admin (one or more regions inside an organization), Chapter officer (one or more chapters, includes both the “officer” and “president” roles), and Member (an active chapter membership with no admin role). Two additional roles only apply to optional modules: Foundation admin and Foundation editor are scoped to one organization’s foundation, and Alumni member is any member whose status is alumni, active alumni, or lifetime alumni.

Higher tiers can always do everything a lower tier can do inside their own scope. Platform admins are exempt from tier checks entirely and can perform any action in any organization.

This page is the source of truth for permissions in GreekManage. If a how-to page elsewhere in the docs implies a role can do something this page says they cannot, this page wins.

Legend:

✅ — can do this action
❌ — cannot do this action
⚠️ — can do this action, but only within a specific scope (see footnote)

How role scope works

Role	Scope of authority
Platform admin	Every organization in the platform
National admin	One organization (its regions, chapters, and members)
Regional admin	One or more regions, and only the chapters inside those regions
Chapter officer	Their own chapter (or chapters, if officer of several)
Member	Their own membership and the chapter they belong to
Foundation admin	One organization’s foundation
Foundation editor	One organization’s foundation (limited to content actions)
Alumni member	The organization where they hold alumni status

Wherever a row says “⚠️ Same chapter only” or “⚠️ Same region only,” the action is allowed but only inside the role’s own scope — a chapter officer of Chapter A cannot take that action against Chapter B.

Authentication and account

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
Sign in with email and password	✅	✅	✅	✅	✅
Sign in with SSO (Google / SAML / OAuth)	✅	✅	✅	✅	✅
Set or change own password	✅	✅	✅	✅	✅
Request own password reset (forgot password)	✅	✅	✅	✅	✅
Reset another user’s password (email link or temporary password)	❌	❌	⚠️¹	⚠️²	✅
Force a user to change password on next login	❌	❌	⚠️¹	⚠️²	✅
Add a secondary email to own account	✅	✅	✅	✅	✅
Verify a secondary email	✅	✅	✅	✅	✅
Set a new primary email on own account	✅	✅	✅	✅	✅
Remove a secondary email from own account	✅	✅	✅	✅	✅
Add a verified email to another user’s account	❌	⚠️³	⚠️¹	⚠️²	✅
Remove a non-primary email from another user’s account	❌	⚠️³	⚠️¹	⚠️²	✅
Register a passkey on own account	✅	✅	✅	✅	✅
Rename or remove own passkey	✅	✅	✅	✅	✅
View another user’s passkeys	❌	❌	⚠️¹	⚠️²	✅
Delete another user’s passkey	❌	❌	⚠️¹	⚠️²	✅
Disable own account	✅	✅	✅	✅	✅
Request own account deletion (30-day grace)	✅	✅	✅	✅	✅
Cancel own pending account deletion	✅	✅	✅	✅	✅
Request own data export (GDPR / CCPA)	✅	✅	✅	✅	✅
Record or revoke own consent records	✅	✅	✅	✅	✅
Configure SSO identity provider (SAML / OAuth) for the organization	❌	❌	❌	✅	✅
Test SSO connection	❌	❌	❌	✅	✅

Members cannot reset their own password from inside the app while signed out — they go through the “forgot password” flow. Chapter officers cannot reset another member’s password; that capability starts at the regional admin tier and is scoped to that role’s chapters. Platform admin passwords cannot be reset by national or regional admins — those accounts manage their own credentials.

Members and directory

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View the member directory for own organization	✅	✅	✅	✅	✅
View a single member’s profile	✅	✅	✅	✅	✅
View another member’s last sign-in time	❌	⚠️³	⚠️¹	⚠️²	✅
View own last sign-in time	❌	❌	❌	❌	❌
Edit own profile (basic fields, degrees, work history, certifications, affiliations, skills)	✅	✅	✅	✅	✅
Edit another member’s membership record (pledge class, graduation year, joined date, chapter custom fields)	❌	⚠️³	⚠️¹	⚠️²	✅
Edit another member’s personal profile or degrees (address, personal email, emergency contact, education)	❌	❌	❌	⚠️²	❌
Change another member’s chapter officer role (officer / president / member)	❌	❌	❌	⚠️²	✅
Change own chapter officer role	❌	❌	❌	❌	❌
Propose a status change for own membership (e.g. active → alumni)	✅	✅	✅	✅	✅
Approve a status change request at the chapter tier	❌	⚠️³	❌	❌	✅
Approve a status change request at the regional tier	❌	❌	⚠️¹	❌	✅
Approve a status change request at the org tier	❌	❌	❌	⚠️²	✅
Submit a member-add request (requires officer or higher)	❌	⚠️³	⚠️¹	⚠️²	✅
Approve a member-add request at the chapter tier	❌	⚠️³	❌	❌	✅
Approve a member-add request at the regional tier	❌	❌	⚠️¹	❌	✅
Approve a member-add request at the org tier	❌	❌	❌	⚠️²	✅
Add a member directly, collapsing the chain (records an override per skipped tier)	❌	❌	❌	⚠️²	✅
Bulk import members (CSV / XLSX)	❌	❌	❌	✅	✅
Delete a membership	❌	❌	❌	⚠️²	✅
Configure profile completeness weights	❌	❌	❌	✅	✅
Send a profile completeness nudge to a member	❌	❌	❌	✅	✅
View directory insights (demographics, completeness)	❌	❌	❌	✅	✅
View the aggregate demographics report (Analytics → Demographics)	❌	❌	⚠️¹	✅	✅
Use the fraternal name check tool	✅	✅	✅	✅	✅
Define custom member fields	❌	❌	❌	✅	✅
Edit chapter-level custom field data	❌	⚠️³	⚠️¹	⚠️²	✅
Edit member-level custom field data	❌	❌	❌	⚠️²	✅
Create or save a custom member view (filter set)	✅	✅	✅	✅	✅
Export the member list to CSV / XLSX	❌⁴	⚠️³⁵	⚠️¹	⚠️²	✅
Collect a finished export file (its download link)	❌	⚠️⁶	⚠️¹	⚠️²	✅

A status change now walks the organization’s configured Member status changes approval chain, the same as a member-add request: it enters at the chapter tier (or the next tier the submitter does not already hold — a national admin’s own submission is auto-satisfied through every tier they hold) and is approved when the chain’s last tier signs off, not by whoever reviews first. Each tier is actioned only by someone who holds it; a national admin gets a permission error attempting to act at the chapter or regional tier. Editing another member’s membership record is allowed for officers in the same chapter, for regional admins inside their region, and for national admins anywhere in the organization — the user’s own role-related fields (officer / president) are off-limits to anyone except a national admin. A member’s personal profile and degrees are narrower: only the member themself and a national admin of their organization can change them. Officers can still read degrees, but not add, edit or delete them.

Family tree (Big / Little lineage)

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View the family tree	✅	✅	✅	✅	✅
Propose a Big-Little relationship for self	✅	✅	✅	✅	✅
Propose a Big-Little relationship on behalf of another member	❌	⚠️³	⚠️¹	⚠️²	✅
Approve a request currently at the chapter tier	❌	⚠️⁷	❌	❌	✅
Approve a request currently at the regional tier	❌	❌	⚠️⁸	❌	✅
Approve a request currently at the org tier	❌	❌	❌	⚠️²	✅
Assign a big/little directly, collapsing the chain (records an override per skipped tier)	❌	❌	❌	⚠️²	✅
Approve own request at any tier	❌	❌	❌	❌	❌

Big/little assignments run on the organization’s big_little approval chain. Any tier the requester holds is recorded as satisfied at submission, so a member’s request starts at the chapter tier, an officer’s at the regional tier, and a regional admin’s at the org tier; a national admin records a pairing in one step, and the platform writes an override for each tier that skipped. An officer or regional admin proposing on behalf of someone else is no longer auto-approved — the request walks the remaining tiers, and the relationship is written only when the chain completes. Either party’s chapter officers may review at the chapter tier, and either party’s regional admins at the regional tier; which tiers apply comes from the little’s chapter.

Engage — forums, posts, and moderation

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
Browse the forum catalog	✅	✅	✅	✅	✅
Create a forum (subject to approval)	✅	✅	✅	✅	✅
Approve or reject a pending forum	❌	❌	❌	⚠️²	✅
Join an open forum	✅	✅	✅	✅	✅
Leave a forum (unless sole admin)	✅	✅	✅	✅	✅
Add a member to a forum (forum admin only)	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Remove a member from a forum	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Change a forum member’s role	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Post in a forum	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Edit own post	✅	✅	✅	✅	✅
Edit another user’s post	❌	❌	❌	⚠️²	✅
Pin or lock a post	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Delete own post	✅	✅	✅	✅	✅
Delete another user’s post	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Comment on a post	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Edit own comment	✅	✅	✅	✅	✅
Delete another user’s comment	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
React to a post or comment	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Attach a file to a post or comment	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Vote in a forum poll	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Mention another member with @	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Save / bookmark a post	✅	✅	✅	✅	✅
Subscribe to a forum’s notifications	✅	✅	✅	✅	✅
Search posts within a forum	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Flag (report) a post or comment	✅¹⁰	✅¹⁰	✅¹⁰	✅	✅
Review a content flag (approve / remove content)	⚠️⁹	⚠️⁹	⚠️⁹	⚠️²	✅
Configure auto-moderation rules (keywords, thresholds)	❌	❌	❌	⚠️²	✅

A “forum admin” is either a national admin of the forum’s organization or a member with the forum-level admin role. National admins always have forum-admin authority on every forum in their organization. Posting, commenting, reacting, and most other in-forum actions require active membership of that specific forum.

Bulletins and chapter activity

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View published bulletins	✅	✅	✅	✅	✅
Create a bulletin	❌	⚠️¹¹	⚠️¹	⚠️²	✅
Edit a bulletin	❌	⚠️¹¹	❌	⚠️²	✅
Delete a bulletin	❌	⚠️¹¹	❌	⚠️²	✅
Publish a draft bulletin	❌	⚠️¹¹	❌	⚠️²	✅
View unpublished or expired bulletins	❌	⚠️¹¹	❌	⚠️²	✅
View a chapter’s activity (chapter page → Activity tab)	⚠️³	⚠️³	⚠️¹	⚠️²	✅
Connect an Instagram social account for the org feed	❌	❌	❌	⚠️²	✅

Regional admins can create org-wide bulletins, but the bulletin’s region targeting determines visibility — they cannot target chapters outside their region. Editing, deleting and publishing a draft are national-admin actions; a regional admin creates only.

Chapter officers post to their own chapter from Bulletins in the chapter sidebar. The audience is locked to their chapter, so an officer can never post org-wide or to a region.

There is no separate Feed any more. It had its own announcements, and having those beside bulletins confused people, so Bulletins is now the only announcement tool. Every Feed announcement was copied into a bulletin when the Feed was removed, and a chapter’s officers can edit the ones they wrote.

Elections

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View list of elections in the organization	✅	✅	❌	✅	✅
Create an election	❌	❌	❌	⚠️²	✅
Edit a draft election	❌	❌	❌	⚠️²	✅
Delete a draft election	❌	❌	❌	⚠️²	✅
Add a position to an election	❌	❌	❌	⚠️²	✅
Add or remove a candidate	❌	❌	❌	⚠️²	✅
Open voting (publish the election)	❌	❌	❌	⚠️²	✅
Preview an election before publishing	❌	❌	❌	⚠️²	✅
Vote in an open election	⚠️¹²	⚠️¹²	⚠️¹²	⚠️¹²	✅
View own past votes	✅	✅	✅	✅	✅
View live vote stats while voting is open	❌	❌	❌	⚠️²	✅
View finalized results	✅	✅	❌	✅	✅
Export election results to XLSX	❌	❌	❌	⚠️²	✅

Only people in an election’s eligible-voter snapshot can vote — the snapshot is captured when the election is published. Finalized results are visible to every member of the organization. Elections are run by national headquarters: regional admins see a “not available for your role” page instead of the elections list and results.

Events and RSVPs

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View events in own organization	✅	✅	✅	✅	✅
Create an event	❌	⚠️³	❌	⚠️²	✅
Edit an event	❌	⚠️³	❌	⚠️²	✅
Delete an event	❌	⚠️³	❌	⚠️²	✅
RSVP to an event	✅	✅	✅	✅	✅
Update or cancel own RSVP	✅	✅	✅	✅	✅
View the attendee list for an event	✅	✅	❌	⚠️²	✅
Check a member in at an event	❌	⚠️³	❌	⚠️²	✅
View the org-wide event calendar	✅	✅	✅	✅	✅

Event creation is gated by chapter officers and national admins. Regional admins have read access to events but do not author them in v0.62.

Photo albums

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own chapter’s albums	✅	✅	❌	✅	✅
Create an album	❌	⚠️³	❌	⚠️²	✅
Edit an album’s title, description, or visibility	❌	⚠️³	❌	⚠️²	✅
Delete an album	❌	⚠️³	❌	⚠️²	✅
Set an album’s cover photo	❌	⚠️³	❌	⚠️²	✅
Upload a photo to an album	✅¹³	✅¹³	❌	✅	✅
Edit own photo’s caption	✅	✅	❌	✅	✅
Edit another user’s photo (caption, featured, removed)	❌	⚠️³	❌	⚠️²	✅
Delete own photo	✅	✅	❌	✅	✅
Delete another user’s photo	❌	⚠️³	❌	⚠️²	✅
Tag a member in a photo	✅¹³	✅¹³	❌	✅	✅
Remove a tag (untag self or a member you tagged)	✅	✅	❌	✅	✅
Remove a tag added by another member	❌	⚠️³	❌	⚠️²	✅

Albums are scoped to a single chapter. Only members of that chapter can view, upload, or tag — regional admins do not have direct access to chapter-scoped photo albums unless they also hold membership in that chapter.

Recognition

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View recognitions on a chapter or member profile	✅	✅	✅	✅	✅
Create or edit recognition categories	❌	❌	❌	⚠️²	✅
Delete a recognition category	❌	❌	❌	⚠️²	✅
Post a recognition to a member	❌	⚠️³	❌	⚠️²	✅
Delete own recognition (the one you gave)	✅	✅	✅	✅	✅
Delete a recognition posted by someone else	❌	❌	❌	⚠️²	✅

Members cannot post recognitions in v0.62; only officers and admins can.

Messages (direct and group messaging)

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
Start a direct message with another org member	✅	✅	✅	✅	✅
Create a group conversation	✅	✅	✅	✅	✅
View messages in a conversation	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	✅
Send a message in a conversation	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	✅
React to a message	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	✅
Rename a group conversation	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	⚠️¹⁴	✅
Add or remove members in a group (conversation admin)	⚠️¹⁵	⚠️¹⁵	⚠️¹⁵	⚠️¹⁵	✅
Leave a conversation	✅	✅	✅	✅	✅
Configure messaging settings for the organization	❌	❌	❌	⚠️²	✅

Messages are private: an org admin cannot read messages in a conversation they are not a member of. Only platform admins bypass this for support purposes.

Notifications

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own notifications	✅	✅	✅	✅	✅
Mark a notification as read	✅	✅	✅	✅	✅
Mark all notifications as read	✅	✅	✅	✅	✅
Configure own notification preferences	✅	✅	✅	✅	✅
Configure own email-digest preferences	✅	✅	✅	✅	✅
Register a push token (mobile)	✅	✅	✅	✅	✅

Dues and chapter billing

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own invoices	✅	✅	✅	✅	✅
Pay own invoice	✅	✅	✅	✅	✅
View chapter-wide invoice list and balance	❌	⚠️³	❌	⚠️²	✅
Initiate a payment on behalf of the chapter	❌	⚠️³	❌	⚠️²	✅
View payment processor configuration (org level)	❌	⚠️³	❌	⚠️²	✅
Configure the org payment processor (Stripe / etc.)	❌	❌	❌	⚠️²	✅
Set dues rates and cadence	❌	❌	❌	⚠️²	✅
View dues rate history	❌	❌	❌	⚠️²	✅
Generate invoices for a billing period	❌	❌	❌	⚠️²	✅
List all org invoices	❌	❌	❌	⚠️²	✅
Export org invoices to XLSX	❌	❌	❌	⚠️²	✅
View list of billing periods	❌	❌	❌	⚠️²	✅
Configure messaging settings (dues reminders)	❌	❌	❌	⚠️²	✅

Manual payment recording, invoice refunds, fee adjustments, and waiver workflows are not exposed in v0.62.1 — adjustments are made through the payment processor’s own dashboard (e.g. Stripe), and the reconciliation happens automatically via webhook.

Foundation

Foundation actions use a separate role model: Foundation admin has full control over the foundation, Foundation editor can author and edit content but cannot manage admins or processors, and national admins have read-only view plus the ability to manage Foundation Admin records.

Action	Member	Chapter officer	Regional admin	National admin	Foundation editor	Foundation admin	Platform admin
View foundation funds and campaigns	✅	✅	✅	✅	✅	✅	✅
Create a fund	❌	❌	❌	❌	✅	✅	✅
Edit a fund	❌	❌	❌	❌	✅	✅	✅
Delete a fund	❌	❌	❌	❌	✅	✅	✅
Create a campaign	❌	❌	❌	❌	✅	✅	✅
Edit a campaign	❌	❌	❌	❌	✅	✅	✅
Activate a draft campaign	❌	❌	❌	❌	✅	✅	✅
Close a campaign	❌	❌	❌	❌	✅	✅	✅
Delete a campaign	❌	❌	❌	❌	❌	✅	✅
View donor records	❌	❌	❌	❌	❌	✅	✅
View donation records	❌	❌	❌	❌	❌	✅	✅
Resend a donation receipt	❌	❌	❌	❌	❌	✅	✅
View own donation history (donor portal)	✅	✅	✅	✅	✅	✅	✅
View own pledges and receipts	✅	✅	✅	✅	✅	✅	✅
View recurring pledges (admin view)	❌	❌	❌	❌	❌	✅	✅
View tax receipts	❌	❌	❌	❌	❌	✅	✅
Trigger annual tax receipt generation	❌	❌	❌	❌	❌	✅	✅
Create or edit a foundation bulletin	❌	❌	❌	❌	✅	✅	✅
Send or schedule a foundation bulletin	❌	❌	❌	❌	❌	✅	✅
Delete a foundation bulletin	❌	❌	❌	❌	❌	✅	✅
Configure the foundation payment processor	❌	❌	❌	❌	❌	✅	✅
Add or remove a Foundation Admin record	❌	❌	❌	⚠️²	❌	✅	✅
Search members to grant foundation roles	❌	❌	❌	⚠️²	❌	✅	✅
Donate to a public campaign	✅	✅	✅	✅	✅	✅	✅

Anyone (signed in or not) can donate to a public campaign through the campaign’s public donate page. Receipts, pledges, and donor history through the donor portal require sign-in.

Learning (courses, quizzes, certificates)

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View courses available to own membership	✅	✅	✅	✅	✅
Take a quiz (start, answer, submit attempt)	✅	✅	✅	✅	✅
View own enrollment progress	✅	✅	✅	✅	✅
Download own certificate	✅	✅	✅	✅	✅
Verify a certificate’s authenticity (public link)	✅	✅	✅	✅	✅
Author a course (create / edit / delete)	❌	❌	⚠️¹⁶	⚠️²	✅
Publish or unpublish a course	❌	❌	⚠️¹⁶	⚠️²	✅
Add or edit a module, lesson, assessment, or question	❌	❌	⚠️¹⁶	⚠️²	✅
Assign a course to a member or cohort	❌	❌	⚠️¹⁶	⚠️²	✅
Create an assignment rule (auto-assign on status change)	❌	❌	⚠️¹⁶	⚠️²	✅
Grade a free-response quiz answer	❌	⚠️³	⚠️¹	⚠️²	✅
View the grading queue	❌	⚠️³	⚠️¹	⚠️²	✅
View the org learning dashboard	❌	❌	❌	⚠️²	✅
View the region learning dashboard	❌	❌	⚠️¹	⚠️²	✅
View the chapter learning dashboard	❌	⚠️³	⚠️¹	⚠️²	✅
View a single course’s dashboard (enrollment progress)	❌	⚠️³	⚠️¹	⚠️²	✅
Export a completion report	❌	⚠️³	⚠️¹	⚠️²	✅
Import legacy completions (CSV)	❌	❌	⚠️¹	⚠️²	✅
Configure org learning defaults	❌	❌	⚠️¹	⚠️²	✅

Chapter officers cannot author courses in v0.62 — that is reserved for regional and national admins. Officers can grade submissions and view chapter-level dashboards.

Compliance

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own chapter’s compliance overview	✅	✅	✅	✅	✅
View own chapter’s requirement list and status	✅	✅	✅	✅	✅
Submit a compliance submission for own chapter	❌	⚠️³	❌	⚠️²	✅
Upload an attachment to a submission	❌	⚠️³	❌	⚠️²	✅
Delete a submission attachment	❌	⚠️³	❌	⚠️²	✅
Download a submission attachment (auth, scoped)	✅¹³	⚠️³	⚠️¹	⚠️²	✅
Approve / reject a submission at the chapter tier	❌	⚠️³	❌	⚠️²	✅
Approve / reject a submission at the regional tier	❌	❌	⚠️¹	⚠️²	✅
Approve / reject a submission at the org tier	❌	❌	❌	⚠️²	✅
Create a requirement	❌	❌	❌	⚠️²	✅
Edit or delete a requirement	❌	❌	❌	⚠️²	✅
Create or edit a requirement template	❌	❌	❌	⚠️²	✅
Create or edit a compliance period (semester)	❌	❌	❌	⚠️²	✅
Generate requirement records for a period	❌	❌	❌	⚠️²	✅
Close a compliance period	❌	❌	❌	⚠️²	✅
Create a requirement override for a specific chapter	❌	❌	❌	⚠️²	✅
Edit or delete a requirement override	❌	❌	❌	⚠️²	✅
View regional submission queue	❌	❌	⚠️¹	⚠️²	✅
View org-wide submission list	❌	❌	❌	⚠️²	✅
Export compliance data	❌	❌	❌	⚠️²	✅
View compliance alert list (chapter)	✅	✅	✅	✅	✅
Act on a compliance alert (acknowledge / resolve)	❌	⚠️³	❌	⚠️²	✅

National admins act at the national tier only. Approving at the chapter or regional tier is refused — a tier is actioned by somebody who holds it. The remedy for a genuinely stuck record is a recorded override (national admins only, reason required), or, where a tier has no eligible reviewer at all, the organization’s Skip tiers with no reviewer setting, which skips it automatically and records the skip. National is never skipped.

PNM (Potential New Members) recruitment

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
Configure PNM application settings (every card)	❌	❌	❌	⚠️²	✅
Configure org slug for the public application URL	❌	❌	❌	⚠️²	✅
Configure consent templates	❌	❌	❌	⚠️²	✅
Create or edit a PNM period (open recruitment window)	❌	❌	❌	⚠️²	✅
Close a PNM period	❌	❌	❌	⚠️²	✅
Submit a public PNM application (no sign-in)	✅	✅	✅	✅	✅
Add a PNM directly to a chapter	❌	⚠️³	❌	⚠️²	✅
View chapter’s PNM list	✅¹³	✅¹³	❌	✅	✅
View org-wide PNM list	❌	❌	❌	⚠️²	✅
Open a PNM application from the review queue	✅¹³	✅¹³	⚠️¹	⚠️²	✅
Edit a PNM profile	❌	⚠️³	❌	⚠️²	✅
Delete a PNM profile	❌	⚠️³	❌	⚠️²	✅
Transition a PNM through intake stages	❌	⚠️³	⚠️¹	⚠️²	✅
Propose a fraternal name for a PNM	❌	⚠️³	⚠️¹	⚠️²	✅
View pending fraternal name approvals (org queue)	❌	❌	❌	⚠️²	✅
Approve or reject a proposed fraternal name at the chapter tier	❌	⚠️³¹⁷	❌	❌	✅
Approve or reject a proposed fraternal name at the regional tier	❌	❌	⚠️¹¹⁷	❌	✅
Approve or reject a proposed fraternal name at the org tier	❌	❌	❌	⚠️²	✅
Upload an attachment to a PNM profile	❌	⚠️³	❌	⚠️²	✅
Delete a PNM attachment	❌	⚠️³	❌	⚠️²	✅
Download a PNM attachment	❌¹⁸	⚠️³	⚠️¹	⚠️²	❌¹⁸
View list of reference letters for a PNM	❌	⚠️³	⚠️¹	⚠️²	✅
Resend a reference-letter invitation	❌	⚠️³	⚠️¹	⚠️²	✅
Submit a reference letter (referee, no sign-in)	✅	✅	✅	✅	✅

Every row in this table additionally requires the Operations module, which is what licenses recruitment (there is no separate PNM module). With Operations off, no role in this table can do any of it, and the public rows are off too — the apply, verification, and reference-letter pages all render a closed state.

Public PNM endpoints (the apply page, email verification, and reference-letter submission) are unauthenticated and rate-limited. PNM transitions, name proposals, and attachments are scoped to anyone who has authority over the PNM’s chapter — chapter officer, regional admin of that region, or national admin.

Alumni

Action	Alumni member	Member (non-alumni)	Chapter officer	Regional admin	National admin	Platform admin
View the alumni directory	⚠️¹⁹	⚠️¹⁹	⚠️¹⁹	⚠️¹⁹	⚠️¹⁹	✅
View the alumni dashboard	✅	✅	✅	✅	✅	✅
Create / edit own mentor profile (becomes a mentor)	✅	❌	❌	❌	❌	✅
List mentors in the organization	✅	✅	✅	✅	✅	✅
Set own alumni privacy preferences	✅	❌	❌	❌	❌	✅
Create a career posting	✅	❌	✅	✅	✅	✅
Edit own career posting	✅	❌	✅	✅	✅	✅
Edit any career posting (admin override)	❌	❌	❌	❌	⚠️²	✅
Delete own career posting	✅	❌	✅	✅	✅	✅
Delete any career posting	❌	❌	❌	❌	⚠️²	✅
Express interest in a career posting	✅	✅	✅	✅	✅	✅
Feature / unfeature a career posting	❌	❌	❌	⚠️¹	⚠️²	✅

Alumni directory visibility depends on each member’s privacy settings — every alumni member can hide their email, phone, work history, and location per-field, with separate visibility levels for “all members,” “alumni only,” and “officers only.”

Retention

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View chapter retention summary	❌	⚠️³	⚠️¹	⚠️²	✅
View chapter retention snapshots over time	❌	⚠️³	⚠️¹	⚠️²	✅
View retention alerts (chapter)	❌	⚠️³	⚠️¹	⚠️²	✅
Acknowledge or resolve a retention alert	❌	⚠️³	⚠️¹	⚠️²	✅
View org-wide retention alerts	❌	❌	❌	⚠️²	✅
Create or edit a member survey	❌	❌	❌	⚠️²	✅
Deploy a survey	❌	❌	❌	⚠️²	✅
View survey results	❌	❌	❌	⚠️²	✅
Respond to a survey you’ve been sent	✅	✅	✅	✅	✅

Documents (governing documents)

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View documents (filtered by visibility)	✅	✅	✅	✅	✅
Upload a governing document	❌	❌	⚠️¹	⚠️²	✅
Edit a document	❌	⚠️³	⚠️¹	⚠️²	✅
Delete a document	❌	⚠️³	⚠️¹	⚠️²	✅
View document version history	✅	✅	✅	✅	✅
Download a document file	✅	✅	✅	✅	✅

Documents have three visibility levels: public (any org member), chapter (chapter members only), and officers (chapter officers only). Members only see documents whose visibility includes them.

AI Services

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
Use the AI chatbot	✅	✅	✅	✅	✅
Receive another member’s phone number or personal email from the chatbot	❌	⚠️³	⚠️¹	⚠️²	✅
Receive a staff-only (private) custom field from the chatbot	❌	❌	⚠️¹	⚠️²	✅
Receive posts from a forum they have not joined via the chatbot²⁰	❌	❌	❌	⚠️²	✅
Configure the org AI provider (Anthropic / OpenAI / Google)	❌	❌	❌	⚠️²	✅
Test the org AI provider credentials	❌	❌	❌	⚠️²	✅
Toggle org AI content scopes (members, forums, compliance, documents, learning)	❌	❌	❌	⚠️²	✅
Trigger an org-level embedding re-index	❌	❌	❌	⚠️²	✅
View embedding job history (org)	❌	❌	❌	⚠️²	✅
Configure the platform default AI provider	❌	❌	❌	❌	✅
Trigger a re-index across all tenants	❌	❌	❌	❌	✅
Parse own resume to enrich profile (AI)	✅	✅	✅	✅	✅
Confirm resume parse results	✅	✅	✅	✅	✅
Request an AI-generated admin report	❌	❌	❌	⚠️²	✅

Audit log and data retention

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own organization’s audit log	❌	❌	❌	⚠️²	✅
View the list of users referenced in the audit log	❌	❌	❌	⚠️²	✅
View the cross-platform audit log	❌	❌	❌	❌	✅
Configure per-org audit retention (days, enabled/disabled)	❌	❌	❌	❌	✅
Request an org-wide data export (admin trigger)	❌	❌	❌	⚠️²	✅
Download a completed org export	❌	❌	❌	⚠️²	✅
Submit platform feedback	✅	✅	✅	✅	✅
View the platform feedback queue	❌	❌	❌	❌	✅

Chapter administration and approvals queue

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
List chapters in own organization	✅	✅	✅	✅	✅
View a single chapter’s details	✅	✅	✅	✅	✅
Create a chapter	❌	❌	❌	⚠️²	✅
Edit a chapter	❌	❌	❌	⚠️²	✅
View chapter stats	✅	✅	✅	✅	✅
List regions	✅	✅	✅	✅	✅
Create or edit a region	❌	❌	❌	⚠️²	✅
Assign chapters to a region	❌	❌	⚠️¹	⚠️²	✅
Remove chapters from a region	❌	❌	⚠️¹	⚠️²	✅
List regional admins	❌	❌	⚠️¹	⚠️²	✅
Add or remove a regional admin	❌	❌	❌	⚠️²	✅
List organization admins	❌	❌	❌	⚠️²	✅
Add or remove an organization admin	❌	❌	❌	⚠️²	✅
List chapter officers across the organization	❌	❌	❌	⚠️²	✅
Edit own organization’s general settings, logo, brand color	❌	❌	❌	⚠️²	✅
View the org-level approvals queue summary	❌	⚠️³	⚠️¹	⚠️²	✅
Submit an account request (public, no sign-in)	✅	✅	✅	✅	✅
Copy or regenerate the organization’s join link	❌	❌	❌	⚠️²	✅
Review an account request at the chapter tier	❌	⚠️³²¹	❌	❌	✅
Review an account request at the regional tier	❌	❌	⚠️¹²¹	❌	✅
Review an account request at the org tier	❌	❌	❌	⚠️²	✅
Add or edit a chapter advisor	❌	⚠️³	❌	⚠️²	✅
Delete a chapter advisor	❌	⚠️³	❌	⚠️²	✅

Per-org storage configuration

Action	Member	Chapter officer	Regional admin	National admin	Platform admin
View own org’s storage configuration	❌	❌	❌	⚠️²	✅
Update own org’s S3 / object-storage credentials	❌	❌	❌	⚠️²	✅
Test the org storage connection	❌	❌	❌	❌	✅
List storage migration jobs	❌	❌	❌	❌	✅
Trigger a storage migration	❌	❌	❌	❌	✅

Platform administration

These actions are reserved for GreekManage platform operators. No tier inside an organization can perform them.

Action	Platform admin
Access the platform dashboard	✅
List every organization on the platform	✅
View an organization’s full platform-level detail	✅
Create a new organization	✅
Toggle a module on or off for an organization	✅
Search users across all organizations	✅
Create a user account directly (no org context)	✅
List, add, or remove other platform admins	✅
List, add, or remove organization admins on behalf of an org	✅
Configure per-org audit-log retention	✅
Configure per-org storage and run migrations	✅
Assign or remove a Foundation Admin record on behalf of an org	✅
Configure the platform-wide email backend	✅
Send a test email through the platform email backend	✅
Configure backup settings (frequency, retention, storage)	✅
Test backup storage credentials	✅
Trigger a manual full database backup	✅
Trigger an on-demand per-org JSON export	✅
List backup history	✅
Download a backup archive	✅
Configure the platform default AI provider	✅
Trigger an embedding re-index across all tenants	✅
Review platform feedback submissions	✅

GreekManage does not currently expose a “suspend organization” action through the API — deactivation is done by toggling is_active directly through platform administration.

Last verified against v0.62.1 (2026-05-10).

Same region only. A regional admin can act on any chapter inside their region, but not on chapters in other regions. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Same organization only. Inside that organization the role can act on any chapter or region. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Same chapter only. A chapter officer can act on members, photos, events, and submissions for their own chapter — not for other chapters in the same region or organization. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Refused by the server, not merely hidden in the interface. A member without an officer role gets a permission error from the export endpoint itself, and the Export button no longer appears on the Members page for them. ↩︎
An officer’s file contains their own chapter’s rows and the public custom field columns. Staff-only (private) custom fields are left out of it — those columns appear only for regional and national admins, matching who can read a private field anywhere else in the product. ↩︎
Their own exports only. A finished file carries whatever the person who requested it was entitled to see, so its download link is not shared sideways: an officer cannot collect a file another officer — or a national admin — asked for, even in their own chapter. Regional and national admins can see any export in their scope. ↩︎
Either party’s chapter. A big/little request’s chapter tier is held by an officer of the big’s chapter or the little’s chapter — cross-chapter pairs are supported, so both have a legitimate interest. ↩︎
Either party’s region. As above, one tier up: a regional admin of the big’s region or the little’s region may act at the regional tier. ↩︎
Forum admin only. Any member can be granted the forum-admin role inside a specific forum; national admins automatically have forum-admin authority on every forum in their organization. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Forum membership required. Joining the forum (or being added by a forum admin) is a prerequisite for posting, commenting, reacting, and voting inside that forum. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Own chapter’s bulletins only. An officer or president can post bulletins to a chapter they are an officer of, and edit, publish or delete the ones their chapter’s officers posted — never an org-wide or regional bulletin, and never one a national or regional admin sent to their chapter. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Eligible voter only. Each election captures an eligible-voter snapshot when it is published; only the people in that snapshot can vote. ↩︎ ↩︎ ↩︎ ↩︎
Chapter member only. The action is allowed for any active member of the chapter, not just officers. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Conversation member only. The action is allowed only if the user is currently a member of the conversation. Org admins cannot read messages in conversations they do not belong to. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Conversation admin only. The group-conversation creator and anyone they promote can manage the membership list. ↩︎ ↩︎ ↩︎ ↩︎
Same region only, and only for courses whose scope is region or chapter-level inside that region — or for org-scoped courses inside the regional admin’s organization. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
The API accepts a review from this tier, but the PNM → Name Check screen is still gated to org admins and platform admins at the page level — there is no chapter- or regional-officer screen to act on it from yet. A record waiting at this tier shows up in a national admin’s queue (it is visible), but approving it is refused with a 403 naming the tier actually awaited — a national admin holds the national tier only and cannot act at chapter or regional on its behalf. There is no override endpoint for this surface either: the only record_override HTTP route in the product is Compliance’s /api/compliance/statuses/<id>/override/, which is specific to ChapterComplianceStatus. The record has no reviewer who can currently reach it. ↩︎ ↩︎
An applicant’s files carry the same personal data as their date of birth and address, so a download link goes only to the people who can read those: an officer of the applicant’s chapter, regional and national admins, and the applicant for a file they upload. Other chapter members, and platform admins with no admin role in the organization, get the attachment list without links — refused by the server, not just hidden in the interface. ↩︎ ↩︎
Subject to each alumni’s per-field privacy settings. A field set to “officers only” is hidden from non-officer members; a field set to “hidden” is hidden from everyone except the owning member and platform admins. ↩︎ ↩︎ ↩︎ ↩︎ ↩︎
Including open forums. Open governs who may join a forum, not who may read it — the forum pages themselves refuse a non-member’s request for posts either way, and the chatbot now matches. Joining is enough. The forum list (names, descriptions, counts) is organization-wide for everyone, in the chatbot and in Engage alike. ↩︎
The API accepts a review from this tier, but Account Requests is a tab on the org admin’s Approvals page, which is national-admin-only at the page level — it is not part of the officer or regional-admin Approvals view. A record waiting at this tier shows up in a national admin’s queue (it is visible), but approving it is refused with a 403 naming the tier actually awaited — a national admin holds the national tier only and cannot act at chapter or regional on its behalf. There is no override endpoint for this surface either: the only record_override HTTP route in the product is Compliance’s /api/compliance/statuses/<id>/override/, which is specific to ChapterComplianceStatus. The record has no reviewer who can currently reach it. ↩︎ ↩︎

Roles overview