Access and roles

Payload roles, what each can do, and how to get access to the project and its services

Payload roles

User accounts in Payload CMS are stored in the execs collection. Each account has a Roles field that controls what they can do in the admin.

Role	What they can do
Admin	Full access to all collections, globals, and settings. Can create and manage other user accounts.
Editor	Can create and edit content across collections. Cannot manage user accounts or change system configuration.

Role-level access control in the codebase is partially implemented. In practice, both roles have broad content access. Check with a maintainer before relying on role restrictions for sensitive collections.

---

Getting access

Payload admin

Access to the Payload admin at https://wlumsa.org/admin requires an account in the execs collection. Contact a maintainer to have an account created for you.

GitHub repository

The repository is at github.com/wlumsa/wlumsa.org. Request access from a maintainer with your GitHub username. You need to be added to the wlumsa organisation.

Vercel

The project is hosted on Vercel. Ask a maintainer to add you to the Vercel team if you need deployment access or need to manage environment variables.

Supabase

The database and file storage run on Supabase. Ask a maintainer for access to the Supabase project if you need to inspect the database or storage bucket directly.

Resend

Email delivery uses Resend. Ask a maintainer for access if you need to manage sending domains, API keys, or review delivery logs.

Stripe

Stripe is used for optional payment features. Ask a maintainer for access if you are working on payment-related functionality.

---

Who to contact

For any access request, reach out to [maintainer name] or email the team at [e-mail].