Organizations
An organization is the group behind one or more marathons: a community, a channel, a charity event that comes back every year. It owns the marathons, layouts, images and the people who work on them.
Creating one
Organizers create organizations from Manage. The name gives the address: "Speedruns Brasil" becomes /speedruns-brasil, with a number added if the address is taken. A few addresses belong to the app itself (events, docs, about and so on) and can't be used. You become the organization's organizer.
The organization page
/<organization> is the home of the organization: its marathons, its layouts with a thumbnail of their first scene, the image library and the base layouts you can start from.
Settings
Admins change the name, the address and the logo on Settings. Changing the address breaks links people saved, and overlay URLs don't change, since they use their own key.
Audit log
Audit log (admins and up) lists who did what: reviews and decisions on signups and donations, saved layout versions, marathon, output and payment account settings, incentives, members and invites. Simple live controls such as the timer, scenes and the ticker, and layout autosaves, are not recorded. Filter by action or person; entries show newest first.
Entries are deleted after the retention period set in Settings, from 7 to 365 days (90 by default). Only the owner can change it, and a shorter period deletes older entries on the next hourly cleanup.
Members and invites
Members lists everyone in the organization with their role. Admins change roles and remove people.
To add someone, create an invite link and send it to them. Whoever opens it while signed in joins with the role you picked. A link works once and expires after 7 days. Invites by email aren't available yet.
Volunteers accepted on a signup also join automatically, see Review.
Roles
Staff roles form a ladder: each one can do everything the roles below it can.
| Role | Can |
|---|---|
| Organizer | everything, including deleting the organization |
| Admin | members, integrations, marathons, outputs and layouts |
| Editor | layouts, marathon settings, signup review, the schedule and incentives |
| Operator | the live dashboard: timer, runs, scenes, feeds, OBS |
Crew roles sit outside the ladder. They give access to one part of the live dashboard and nothing else:
| Role | Can |
|---|---|
| Runner | see the timer and run; watch their own feeds; start, pause and finish their own timer when the marathon allows it |
| Host | edit the run and the upcoming list, the ticker and the music |
| Commentator | see the timer and run; watch every runner's original feeds |
| Moderator | the donation queue, with the timer and run read-only |
| Beneficiary | connect and disconnect the account that receives the donations |
Crew never see output keys, scenes or OBS controls. The details are in Crew roles on the dashboard.
Layouts
The Layouts section lists the organization's layouts. Create one from scratch, or pick a base layout under "Start from a template" and press Use this layout to get your own copy. Open a layout to edit it in the editor.
Deleting a layout moves it to the trash, where admins can restore it.
Base layouts
Three base layouts come with the app. They share the same scenes and differ in look:
- Minimal: flat, rounded panels on a soft dark gradient, one accent color.
- Neon: a dark grid with glowing cyan and magenta outlines.
- Classic Bar: dark bars with diagonal stripes on a teal backdrop, the look of the old PHP layouts.
Each one has the scenes a marathon usually needs: setup (between runs), countdown, normal-16x9, normal-4x3, races of 2 (16:9 and 4:3), 3 and 4. Every scene has a backdrop with holes where the game and webcam go, so OBS captures show through. Your copy is yours to change: the repeated parts are components and the omnibar is a block, so a change there reaches every scene.
Images
The image library holds logos, backgrounds and anything else a layout shows. Upload with the button or by dropping files on the page. In the editor, image settings open the same library, and uploading there picks the new image at once.
Deleting an image that a layout uses leaves an empty spot where it was.