Skip to main content
Orgo is designed to work for thousands of different organizations, but your scouting troop isn’t an engineering company. Customization lets you change the language, rename “Members” to “Scouts”, rearrange the sidebar, configure the dashboard, and import your existing data — all without writing code or touching the underlying system. Settings → Customization
All customization features require Tenant Admin permissions. Only organization administrators can access the Settings menu.

What you can customize


When setting up a new organization, customize in this order to avoid rework:
1

Set the default language

Go to Settings → Customization → Languages. Enable the languages your members speak and set the primary default. Do this first so everything is in the right language from day one.
2

Customize terminology

Go to Settings → Customization → Labels. Rename the 5-6 terms that differ for your organization (e.g., “Members” → “Scouts”) before anyone sees the platform. You’ll need to provide translations for each active language.
3

Import existing data

Go to Settings → Customization → Import Data. Bring in your member database from CSV. Import in this order: Local Centers first, then Roles/User Types, then Members — so references resolve correctly.
4

Organize the sidebar menu

Go to Settings → Customization → Menu Organizer. Hide modules you’re not using, move important items to the top, and set permission-based visibility for each category.
5

Configure the dashboard

Go to Settings → Customization → Dashboard Organizer. Pick 3-5 widgets that matter most — upcoming events, recent discussions, quick links — and arrange them by priority.
6

Write a welcome message

Go to Settings → Customization → Dashboard Welcome. Greet members with a personalized message. Use dynamic fields to personalize the greeting and target specific user types if needed.
You can change all of these settings at any time. But getting languages and labels right before inviting members saves confusion — members won’t see outdated terminology during onboarding.

Real-world example

Scenario: A national scouting organization with 5,000 members across 150 troops, operating in French and German.
  1. Languages: Enable French (default) and German. Members choose their preference on first login.
  2. Labels: Rename “Members” → “Scouts”, “Groups” → “Patrols”, “Local Center” → “Troop”, “Events” → “Activities”.
  3. Import: Upload troop list (CSV with troop names and regions), then import scout database with troop assignments.
  4. Menu: Hide “Fees”, “Newsletter”, and “Courses” since the org doesn’t use them yet. Move “Activities” (events) to the top.
  5. Dashboard: Enable Upcoming Activities, My Patrol, and a Welcome Message.
  6. Welcome: A personalized greeting using dynamic fields — each scout sees their own name and troop.

Troubleshooting

Customization requires Tenant Admin permissions. If you’re a local admin or regular member, ask your organization’s main administrator for access.
Most customization changes apply immediately. If members don’t see updates, ask them to refresh their browser. For language and label changes, members may need to log out and back in for all cached text to update.
Each customization tool has its own reset option. The Menu Organizer has a “Restore Defaults” button. For labels, clear individual overrides. For the dashboard, remove categories and re-add the defaults. There’s no single “reset everything” button — this prevents accidental resets.

  • Branding — Visual customization (logos, login background)
  • Modules — Enable/disable platform features
  • Organization Info — Name, contact details, and financial settings