Organization
As an Org Admin you manage your organization's settings. All content, runs and user accounts belong to exactly one organization — what you set here applies to everyone in it.
You find the settings in the left menu under Admin → Settings. The page has two tabs: General and Legal.
"General" tab
| Field | Meaning |
|---|---|
| Name | The organization's display name. It appears in the application header. Required. |
| Slug | The short name used in URLs and interfaces (e.g. stadt-augsburg). Not editable — it is fixed at registration and stays permanent so existing links and access remain valid. |
| Content languages | The languages in which multilingual content can be maintained (titles, descriptions, task texts). |
Changes take effect only when you click Save; the button stays inactive until you change something.
Understanding content languages
Content languages decide which language tabs creators see on a piece of content — not the display language of the interface.
- German is always enabled and cannot be removed.
- If you add English, for example, rallyes, stations and challenges gain an "English" tab where creators can enter the text.
- Pick from the list or type any ISO language code (e.g.
ukfor Ukrainian,arfor Arabic). - Participants choose their language when they join. If a text is missing in their language, the German text is shown — so there is never a gap.
Order matters
Set the content languages before creators start. If a language is added later, existing content is empty in that language and has to be filled in.
"Legal" tab
Here you store your organization's imprint and privacy policy. Both are reachable for participants inside the application.
- The fields offer a simple editor (bold, italic, underline, headings, lists, links).
- Empty fields fall back to the template. As long as you enter nothing, the shipped default text is displayed.
- For production use, replace both with your organization's own reviewed texts.
Your responsibility
Imprint and privacy policy are legally binding statements by your organization. The shipped templates are placeholders, not legal advice.
What else belongs to setup
| Step | Where |
|---|---|
| Create accounts and assign roles | Users · Roles |
| Understand two-factor authentication (mandatory for admins) | 2FA |
| Trace who did what | Audit log |