Appearance
Global Settings
The Settings area is where system-wide configuration is managed — mostly Super Admin territory. This includes roles and permissions, offline payments, email configuration and daily digest, LGL connection, and global assets. This page gives an overview of the settings hub and how to view or change staff roles safely.
Used by: Super Admin (and Admin where permitted).
What the Settings Area Is For
Settings control how the application connects to external services (Stripe, LGL, email), who can do what (roles), and shared resources (e.g. logos). Changing settings can affect the whole system, so only Super Admins should change sensitive items; some screens may allow Admin only where the API permits. Daily member-facing work (members, enrollments, payments, messaging) does not require opening Settings unless you’re updating something specific.
Settings Hub Overview
Settings is now organized as a left sidebar with grouped accordion navigation. Go to /admin/settings to open the hub; the sidebar expands the group for your current page automatically.
Payments
| Section | Path | What it covers |
|---|---|---|
| Stripe | /admin/settings/stripe | Payment connection and related options. |
| Fee Pass-Through | /admin/settings/fees | Enable or disable the processing fee pass-through; set the rate (default 2.9% + $0.30). When enabled, the portal checkout shows a Processing fee line and members pay the grossed-up total so the org nets the full product price. |
| Offline Payments | /admin/settings/offline-payments | Enable offline checkout, set hold periods, mailing address, and office info. See Offline Payments. |
Integrations
| Section | Path | What it covers |
|---|---|---|
| LGL | /admin/settings/lgl | LGL API connection (URL, keys). Change only when directed by Andrew. |
| Data Import | /admin/settings/data-import | Import tools for bulk data. |
| Embed | /admin/settings/embed | Generate embed snippet code for embedding the classes or events widget on an external site (e.g. WordPress). Copy the generated script tag and paste it into your site. |
Communications
| Section | Path | What it covers |
|---|---|---|
| Email Config | /admin/settings/emails | Email/SMTP configuration and the daily digest toggle. |
| Notifications | /admin/settings/notifications | Route each admin alert category to specific staff. See Notification Preferences. |
| Renewal Reminders | /admin/settings/renewal-reminders | Set the timing preset for automated membership renewal reminder emails. See Renewal Reminders. |
Site
| Section | Path | What it covers |
|---|---|---|
| Global Assets | /admin/settings/assets | Global assets such as logos or shared images used in emails or the site. |
Roles are managed at /admin/settings/roles — not listed in the settings groups above. Open it from Roles & Permissions in the main admin sidebar, or go there directly.
Roles and Permissions
How to View Staff by Role
- Go to https://admin.uibeta.org/admin/settings/roles (Staff Roles & Permissions).
- The staff table lists each Staff Member with their Effective Role. It works like the People list: search by name or email, filter by role (Super Admin, Admin, Instructor), and click the column headers to sort.
- Below the table, the permissions grid shows what each role can do by default. Use Overlay a staff member's effective access to pick one person and see where their access differs from their role's default. Those cells are tinted and tagged Custom.
- + Invite Staff Member (top right) creates a new staff account.
How to Change a Staff Member’s Role
- Go to https://admin.uibeta.org/admin/settings/roles.
- Find the person and click Manage Role, then choose the new role (User (No Admin Access), Instructor, Admin, or Super Admin).
- Save. The change takes effect immediately — they will see only what their new role allows.
WARNING
Changing roles affects what staff can see and do immediately. Double-check before saving.
What Each Role Can and Cannot Do
| Role | Can do | Cannot do |
|---|---|---|
| Super Admin | Full access: settings, roles, LGL config, all members, memberships, classes, events, payments, campaign messaging, email templates, coupons, etc. Always has every permission. | — |
| Admin | Members, memberships, classes, events, enrollments, registrations, campaign messaging, email templates, coupons, sync view — most of the admin panel. Payment and refund access is a separate permission (Manage Payments) that can be turned off for an individual admin — see Fine-Tuning an Admin's Access below. | Change system settings (Stripe, LGL API, SMTP), manage staff roles, or grant permissions — those are Super Admin only. |
| Instructor | Assigned classes and rosters; instructor Messaging (email your class roster); Profile; view enrollments for their classes. | Admin panel, campaign messaging, payments, member records beyond roster, LGL sync, settings, coupons, or other admin-only areas. |
Fine-Tuning an Admin's Access (Per-Person Permissions)
A staff member's role sets their baseline, but you can turn individual capabilities on or off for each person. This is done on the person's own page, not on the Roles screen:
- Open the staff member from People (Member 360) (
/admin/users, then click their name). - Scroll to the Permissions card. It only appears for staff accounts.
- Tick or untick a checkbox to grant or remove that capability. Changes save as you click. A capability that differs from the role's default is marked as an override.
- Reset to Defaults removes every custom override and puts the person back on their role's defaults.
Only Super Admins can change these checkboxes. Other staff see them but cannot edit them.
The most important one is Manage Payments — this controls whether that admin can issue refunds and manage payment records. Turn it off to create an Admin who can do everything except refunds.
Example — an admin who should not issue refunds: set the person's role to Admin, then uncheck Manage Payments. They keep access to members, memberships, classes, events, enrollments, coupons, and messaging, but the refund controls are removed.
Continuity tip
Make sure at least two people have Manage Payments enabled. If only one person can issue refunds and they are unavailable, a Super Admin has to step in and re-grant the permission before any refund can go through.
TIP
Super Admins always have every permission — you cannot remove a capability from a Super Admin. Per-person fine-tuning applies to Admins and Instructors.
Instructors and student email lists
Instructors have a Download Student Email Lists permission, which lets them export the email addresses of students in their classes. It is on by default for every instructor. To stop one instructor from exporting emails, open their page, find the Permissions card, and untick Download Student Email Lists. Other instructors are not affected.
Global Assets
/admin/settings/assets is where you upload and manage global assets (e.g. logos, shared images) used in emails or across the site. Upload or replace files here; product-specific or page-specific images may be managed elsewhere (e.g. media or product settings).
LGL Settings — Important
WARNING
LGL API settings in /admin/settings/lgl should only be modified by Andrew. Incorrect configuration will break all LGL sync. If sync is failing, retry failed jobs from /admin/sync first; if the same jobs keep failing, contact Andrew before changing any LGL settings.
Summary
- Settings hub: Admin → Global Settings (
/admin/settings) — sidebar accordion grouped into Payments, Integrations, Communications, and Site. Roles are at/admin/settings/roles. - Roles: Change with Manage Role on Roles & Permissions (
/admin/settings/roles), or with the Staff Role field when editing a user’s detail page, as Super Admin; changes apply immediately. - Per-person permissions: Use the Permissions card on the person's page (
/admin/users/[id]). - LGL: Do not change LGL settings unless Andrew asks you to.
Need help? Contact Andrew.