| title | Access and roles |
|---|---|
| description | Payload roles, what each can do, and how to get access to the project and its services |
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. |
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.
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.
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.
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.
Email delivery uses Resend. Ask a maintainer for access if you need to manage sending domains, API keys, or review delivery logs.
Stripe is used for optional payment features. Ask a maintainer for access if you are working on payment-related functionality.
For any access request, reach out to [maintainer name] or email the team at msa@wlu.ca.