Settings reference

⋮→Settings in the app, admins only. Eight tabs; this page goes through each one. Nothing here is saved until you press Save ✓, with two exceptions noted below that take effect the moment you press their own button.

Settings works even with the board offline

Deliberately. This is where you go to fix a connection, so the app never locks you out of it — unlike the rest of the app, which goes read-only when the mixer is unreachable.

👥 Team

Who this server belongs to. Sign-in, roles and invitations are managed on the website, not here — members of your church appear as musicians in the app automatically.

Team tab
Status	Whether this server is connected to a church account, and whether it can currently reach the cloud.
Signed in as	The account being used on this device right now.
Server Name	What this installation is called on the website's Servers page. Worth setting if you have more than one — 'Main Sanctuary', 'Chapel'. Press Save Server Name.
↻ Refresh Team Roster	Pulls the member list from the website immediately, instead of waiting for the next automatic sync. Use it after inviting someone if they haven't appeared yet.
Sign Out of This Device	Ends the session on this console. The server stays connected to your church.

📁 Folders

Folders are the headings musicians are grouped under on the roster. They're for your own convenience — they have no effect on audio.

+ Add Folder creates one.
Drag the ⠿ handle to reorder. This is the order they appear in on the roster.

🎤 Mics

The microphones available to assign to musicians. Each one is identified by its physical source input number on the X32 — the socket the cable or receiver is plugged into, not the channel strip number — with a friendly label shown in the app.

Name them after the microphone, not the person: “Wireless 3”, “Lav Mic 1”, “Pastor Mic”. The person's name is what you assign to it.

⬇ Import All Named Channels from X32 reads the board and offers everything you've already named there, so you can tick the ones you want instead of typing them again.

Twelve characters

The X32 truncates channel and bus names at twelve characters, and the app writes a musician's name onto whichever channel their microphone lands on. Longer names still work — they're just cut short on the board's own display.

🎛 Sends

Audio sources that aren't someone's microphone: instruments, click tracks, backing tracks, a playback machine. Musicians can add any of these to their monitor mix.

The name must match the channel name on the X32 exactly. That's how the app finds it — a typo means the send does nothing.
Each send gets an icon, guessed from its name. Change it if the guess is wrong.
Drag ⠿ to reorder the list musicians choose from.
⬇ Import All Named Channels from X32 avoids the typo problem entirely — take the names from the board.

🔊 Monitors

The monitor mixes available to assign — in-ear packs and wedges. Each is identified by its X32 bus number, with a friendly label shown in the app.

Name them so a volunteer can identify theirs: “Pack A”, “Drums Wedge”, “Podium Monitor”. ⬇ Import All Named Buses from X32 pulls the names you already gave the buses on the board.

🎚 X32

How the app reaches your mixer. Both halves of this tab take effect immediately — they don't wait for Save ✓.

🔍 Scan Network for Boards looks for X32 and M32 consoles on the local network and lists what it finds. Press Connect on the right one.
✏️ Enter Board IP Manually is the fallback if the scan comes up empty. Type the board's IP address, leave the port at 10023 unless you have a reason not to, and press Save & Reconnect.

The status card underneath tells you where you stand:

Connection status
✅ X32 Connected and Ready	Everything is working.
⏳ Downloading Configuration…	The app is reading the board's channels and buses. It shows a percentage; changes are refused until it finishes.
❌ No X32 Found / Not Connected	Check the address, that the board is powered on, and that it's on the same network as this PC.

Leaving the address blank lets the app discover the board itself. See network & remote access for why a wired connection to the board matters.

📋 Logging

The log level controls how much detail the server records. Changes take effect immediately, with no restart.

Leave it on INFO normally.
Switch to DEBUG when you're chasing a problem, or when support asks. It writes a lot more, so put it back afterwards.

The tab also shows the full path to the log file, which is the thing to attach to a support email. The server keeps the last ten runs and starts a fresh file each time it launches.

ℹ️ About

The installed version number. Worth quoting in a support email, and worth checking against the latest release before chasing a bug.