White-label branding & customization

Point a subdomain of your own domain at the platform, for example community.yourorg.org or members.yourorg.org. Every page, link, and login URL then uses your address instead of orgo.space.

Connecting the domain is a single DNS change:

• Add a CNAME record pointing your chosen subdomain at the platform
• Orgo issues the SSL certificate and renews it automatically
• New workspaces start on an orgo.space subdomain, so nothing is blocked while DNS is being arranged

The configuration itself takes minutes. DNS propagation is usually the longest part.

There is no Orgo logo, no Orgo link, and no "Powered by" badge on any screen a member reaches. Members who never open the administration area have no reason to know which platform sits underneath.

Your organization name, country, and slug feed page titles, footers, and system-generated content, so the platform refers to your organization by name rather than by a generic label.

Orgo takes four separate uploads and selects the right one per context:

• Full logo for light backgrounds
• Full logo for dark backgrounds
• Square icon for light backgrounds
• Square icon for dark backgrounds

Full logos appear in navigation headers and email templates. Square icons cover the favicon, mobile bookmarks, and compact interface elements.

Set your two brand colors and Orgo applies them to buttons, links, headers, navigation, and interactive components across every page. Changes take effect immediately, with no rebuild and no code.

Orgo ships several interface themes, including a full light and a full dark version. Your organization sets the default theme for everyone, and members can switch to a different one for their own account.

Authentication is often the first screen a member sees, so it carries the full identity:

• Your logo on the sign-in page
• A background image you upload for the login and registration screens
• The same branding on sign-up, password reset, and two-factor screens

Each member type can be given its own color, which then appears in member listings and reports. Full members, students, volunteers, and staff become distinguishable at a glance.

Orgo includes a menu organizer for both the member-facing menu and the administration menu:

• Rename any menu item to your own terminology
• Reorder items by drag and drop
• Hide items your organization does not use
• Add your own links, internal or external, for example your public website, a member handbook, or a donation page

Every menu item can be shown or hidden per role permission and per user type. A volunteer, a chapter admin, and a finance manager open the same platform and get three different menus, each containing only what that role actually uses.

This keeps the interface short for ordinary members and removes the need to explain which items to ignore.

Menu items can carry an emoji and a color. A long navigation list becomes easier to scan, and the platform takes on your organization's character rather than a default one.

Each group and each project can carry its own emoji, alongside its own color. Chapters, committees, working groups, and projects become recognizable at a glance in the sidebar and in listings instead of reading as one uniform list.

The dashboard is assembled from drag-and-drop widgets, and the welcome message can differ per user type. New volunteers and new full members can be greeted with different wording and different next steps.

Nearly every module and listing can be switched off for your organization. If you do not run votes, courses, or gamification, those items do not appear in the menu at all.

Any label or string can be replaced. Search for the wording you want to change, enter your own, and it changes everywhere in the interface. Organizations use this to turn "local group" into chapter, branch, section, or unit, or to rename voting to polls.

Overrides can be entered one at a time, or supplied wholesale as a language file for the whole organization.

Roles carry the names your statutes use, and each one maps onto a documented permission level. The title can be anything your organization calls it while the underlying access rules stay consistent and auditable.

Members are not forced into one language:

• Enable only the languages your members actually use
• Members choose their own language, or your organization forces a default
• Browser settings can select the language automatically on a first visit

New languages are deployed on request rather than waiting for a release cycle, and each organization can keep its own translation overrides on top of the standard ones.

System emails go out under your organization's name and contact details. Members see a message from your organization, not from a software vendor they have never heard of.

Email headers and footers carry the rest of your identity:

• Your logo in the email header
• Your email address, phone number, and postal address in the footer
• Links to your Facebook, LinkedIn, Twitter, Instagram, and YouTube profiles

Welcome emails, invitations, renewal reminders, payment confirmations, event confirmations, and donation receipts all run on templates you can rewrite. If the default wording does not sound like your organization, replace it.

Branding applies to the whole set. Invitations, confirmations, and automated reminders carry the same identity as a designed newsletter campaign.

Every organization can use the standard Orgo Community app on iOS and Android at no extra cost. Members download it, sign into your workspace, and get discussions, events, media, messaging, and push notifications straight away.

As a paid add-on, Orgo publishes a white-label version of the app under your organization's name and icon, so members search for and download your app rather than Orgo's.

The add-on is quoted separately, because each app needs its own store listing, its own screen assets, and ongoing maintenance as the platform changes.

The app is an interface over the same workspace. Nothing has to be built twice, and the choice between the standard app and a branded one can be made later without changing how the platform is set up.

These components drop into an existing site with no Orgo branding attached:

• Registration forms, including one form per member type
• Donation widgets, pop-ups, and sticky donate buttons
• Newsletter signup forms
• Public event listings and event pages
• A chapter map that updates itself as chapters change

Add a member portal or login button to your website that takes members straight into your workspace at your own domain, so the handover from public site to member area does not look like a jump to a different product.

Orgo can act as the identity provider for your other tools, so an online shop or a custom app can offer a login button branded with your organization's name and backed by your member database.

Videos hosted in Orgo play in a player carrying your organization's logo, and keep that logo when embedded on an external site, instead of showing a third-party platform's brand on your own content.

This is a deliberate product decision. Public-facing design stays on your own site, where your team already controls it, and Orgo supplies the member-facing parts that embed into it.