System settings.

System Settings gives you complete control over your application's branding, member experience, email configuration, compliance features, and loyalty card behavior from one dashboard.

Accessing system settings

1. Sign in to your admin dashboard
2. Navigate to Settings in the admin sidebar
3. Pick an area from the side navigation to open its settings

Who can access this

Only Super Administrators (the highest admin role) can view and modify system settings. This ensures critical configuration stays protected.

Configuration areas

System Settings is organized into sections you move between from a side navigation. It opens on an Overview that names every setting in one place: a card for each section below, plus cards for the app surfaces that hold their own controls (License and updates, Health center, and, for full administrators, SaaS overview, Plans, and Provider credentials; Agent keys appears when the Agent API is enabled). Select a card to open its section or surface. A section also opens from a bookmarked link and skips the Overview.

---

Section overview

Branding

Customize your application's identity and appearance.

Logo Guidelines:

• SVG format recommended for crisp scaling
• Horizontal logos work best (max 200×60px display)
• Use transparent backgrounds when possible
• Accepted formats: SVG, PNG, JPG, and WebP (max 2MB)

Favicon Guidelines:

• Accepted formats: .ico (traditional) or .svg (modern, scalable)
• Max file size: 512KB
• If no custom favicon is uploaded, the default favicon.ico is used
• The app applies the brand color as the browser theme color

---

Homepage

Configure how visitors experience your public landing page.

Showcase options

When the Showcase layout is selected, the section shows its extra settings:

Full guide: Homepage Layout

---

Onboarding

Configure how new members join and interact with your loyalty programs.

Partner registration

Control whether businesses can create their own partner account, and what happens when one signs up.

Where the notification goes: the app sends it to APP_ADMIN_EMAIL if you set one, otherwise to the root admin address captured at install. If neither is a real address, it skips the email and records a short note in the log instead. Demo installs send neither email.

Full guide: Partner Registration

Member cards

Full guide: Member cards admin setup

Anonymous members

Enable zero-friction onboarding for visitors.

How it works: Visitors become members at once. No signup required. They can earn points, collect stamps, and claim rewards right away. To access their account on other devices or receive emails, they can add an email address at any time.

Full guide: Anonymous Members

---

Compliance

Privacy and regulatory compliance settings.

GDPR & Privacy Compliance: When enabled, visitors will see a cookie consent banner before any tracking cookies are set. This helps ensure compliance with GDPR and similar privacy regulations.

Full guide: Cookie Consent & Compliance

---

Email settings

Configure how emails are sent from your application.

A live Email Preview shows how emails will appear to recipients.

Note: SMTP and email provider settings must be configured in .env. See Email Configuration for provider-specific setup.

---

Loyalty cards

Control loyalty program behavior, limits, and security settings.

Member settings

Redemption settings

Staff settings

Privacy & Security Notice: This setting helps protect member privacy by limiting how long staff can view member interaction history. Lower values improve privacy but may reduce staff efficiency.

Full guide: Loyalty cards Settings

---

PWA

Configure installable app settings and icons for the Progressive Web App.

HTTPS Required: PWA features require HTTPS (SSL certificate) to work.

App icons

Upload square PNG images for home screen and app drawer. The app resizes the icons.

Icon Guidelines:

• Use square images (1:1 aspect ratio)
• PNG format recommended for best quality
• Solid background color works best (avoid transparency)
• Use your brand colors and logo

Full guide: PWA Configuration

---

Integrations

Turn features on or off, and check your Google Wallet connection. This section is always available.

Feature switches

Each switch turns a feature on for the whole installation. A saved switch overrides the matching .env flag, so you can manage these without editing files or restarting.

Google Wallet is a plan feature, not a switch. Gold and Platinum include it by default; an operator sets it per plan on the Plans page, with a per-partner override on the Permissions tab. You configure only its credentials here, in the Google Wallet card right below the switches. See Google Wallet Integration.

Outbound webhooks are not a switch here. Webhooks comes with a partner's plan (Gold and Platinum include it by default), turned on or off per tier from the Plans editor, with a per-partner override on the Permissions tab. See Webhooks overview and setup.

Google Wallet credentials

Right under the integration switches, the Google Wallet card shows a configured/not-configured badge and lets you enter the credentials. These save together with the rest of the settings page.

The encrypted JSON overrides the environment value. You can still set GOOGLE_WALLET_ISSUER_ID and the credentials in .env instead. See Google Wallet Integration for the full setup.

Once the credentials are saved, a Test connection button appears on the card. It runs a live check that the service account can authenticate with Google and reports a short status. It confirms the credentials only, not the issuer permissions or whether passes will provision, which stay Google-side, and never shows the credential value.

Note: A switch you save in the dashboard wins over its .env flag. Leave a switch untouched and the .env value (or the built-in default) applies. Use Reset on a setting to return to the .env value.

---

How settings work

Settings you configure here take priority over everything else:

Once you save a setting in the dashboard, it overrides any defaults or environment variables.

Tip: Use the dashboard for settings you want to manage. Use .env for settings you want to lock in at the server level.

---

Key concepts

Demo mode protection

If your application is running in demo mode (APP_DEMO=true), you won't be able to save or reset settings. This protects demo installations from changes.

Audit logging

The system logs every change you make. It records:

• Who changed what
• When they changed it
• Old and new values

This creates a complete audit trail for compliance and troubleshooting. See Activity logs for more details.

---

Related topics

• Anonymous members: Zero-friction onboarding
• Homepage layout: Smart Wallet, Showcase, Portal, and Public Listing layouts
• Branding: Name, logo, and URL configuration
• Email configuration: Sender settings and SMTP providers
• Cookie consent & compliance: Privacy and GDPR settings
• Loyalty cards settings: Card behavior and limits
• PWA configuration: Progressive Web App settings
• Google Wallet Integration: Member passes for Android
• Activity logs: View all setting changes