Organization settings overview
Organization settings are the controls that shape how Lurno looks and behaves for everyone in your workspace — whether that workspace is a company, a SaaS customer academy, a university, or a school. This is where you set your visual identity, review how people sign in, register the domains you use, and define your own roles and member fields.
What this does
Section titled “What this does”Organization settings apply to the active organization — the one shown in the organization switcher at the top of the sidebar, not the whole tree at once. If you administer sub-organizations, switch to a sub-organization first and its settings open in that scope.
Before you start
Section titled “Before you start”- You need permission to update the organization. Without it the page redirects you to My Organizations — it isn’t shown read-only.
- Check the organization switcher before you change anything. Branding, domains, roles and custom fields are all per-organization.
- Domains only appears if you hold the separate organization-domain permission, so two colleagues can see different tab rows on the same page.
The tabs
Section titled “The tabs”Open Org settings from the Settings section of the sidebar. The page is headed Organization settings. You’ll find these tabs:
- Branding — theme template, light/dark mode, logos, favicon, platform title and slogan, login-page backgrounds, and per-token colour overrides. See Branding & theming.
- Groups — audience groups, which decide the experience profile, theme and assets a matched learner sees. These are not the same as the people groups on the Groups page; see Groups for those.
- Sign-in methods — a read-only status list. Email and password is marked Enabled; single sign-on, passkeys and multi-factor are marked Coming soon and are not configurable here. See Single sign-on for what does exist today.
- Email templates — the catalogue of transactional emails sent on your organization’s behalf, and the variables each one can render. The editor isn’t available yet; every template currently uses the platform default copy.
- Notifications branding — the header and footer used in your notification emails. You pick a header layout and a footer layout, fill in slots (logo URL, tagline, address, brand colour, social links) or drop to raw HTML, and a preview pane renders the result as you go.
- Notification domains — the sending domain your notification email comes from. See Email from your domain.
- Embed domains — which external domains may be framed inside the learner player. Leave the list empty to allow any
httpsembed; add a domain to restrict to your list (known video providers are always allowed). - Domains — serve the app on a web address you own. Only shown if you hold the organization-domain permission. See Connecting a custom domain.
- Integration — the partner integration panel. It starts with a single Enable partner integration button; once enabled it shows the API base URL, this organization’s account code, a table of account codes for every sub-organization, and a Rotate API key control.
- Roles — the roles your organization defines and the permissions each one grants. See Roles & permissions.
- Custom fields — typed attributes your organization collects on members. Two visibility levels are enforced today: Admin only and Self-editable; the others are marked as coming soon.
Settings that live somewhere else
Section titled “Settings that live somewhere else”Several things people expect to find here are on other screens:
| What you want | Where it actually is |
|---|---|
| Create or arrange sub-organizations | My Organizations — see Sub-organizations & structure |
| Default language, timezone, renamed terms | My Organizations → open an organization → Language Settings — see Terminology |
| Module access for a sub-organization | My Organizations — the modules control on an organization row that has sub-organizations of its own |
| AI provider keys, email sending keys | Integrations in the sidebar, which needs its own integrations permission — see Integrations overview |
| Your plan, its caps and which modules it includes | Set by Lurno on your subscription package — see Plans & billing |
| Structure levels (the tiers sub-organizations sit at) | Defined by Lurno for your tenant; not self-serve |
Reference
Section titled “Reference”| Tab | Controls | Who sees it |
|---|---|---|
| Branding | Theme, logos, favicon, titles, login backgrounds | Anyone who can open the page |
| Groups | Audience groups and their experience profiles | Anyone who can open the page |
| Sign-in methods | Read-only status of available sign-in methods | Anyone who can open the page |
| Email templates | Transactional email catalogue (read-only today) | Anyone who can open the page |
| Notifications branding | Notification email header, footer and preview | Anyone who can open the page |
| Notification domains | Sending domain for notification email | Anyone who can open the page |
| Embed domains | Allowed external embed hosts in the player | Anyone who can open the page |
| Domains | Custom hostnames for this organization | Needs the organization-domain permission |
| Integration | Partner API key and account codes | Anyone who can open the page |
| Roles | Org-defined roles and their permissions | Anyone who can open the page |
| Custom fields | Typed member attributes | Anyone who can open the page |
Troubleshooting
Section titled “Troubleshooting”The whole page bounces me away. You don’t have permission to update the active organization. The route redirects to My Organizations rather than showing a read-only view. Confirm on Plans, permissions & modules.
The Domains tab isn’t there. That tab needs the organization-domain permission on this organization specifically. It’s separate from the permission that opens the rest of the page.
My changes landed on the wrong organization. Every tab writes to the organization currently selected in the organization switcher. Switch first, then edit.
I can’t find sub-organizations or terminology here. They aren’t on this page — see the table above.
I can’t edit an email template. The template editor isn’t available yet. Every template uses the platform default copy; the tab shows the catalogue and the variables each template can render.