Settings holds everything that applies to your whole platform rather than to a single course or member: its name and look, the features it offers, who on your team may do what, and the connections to other tools. This article shows how the area is organized and who can open which part of it.
Where to start
Settings sits in the admin menu as Settings. Its first page, Most used, collects the settings most people need as cards: Name & language, features, Logo & colors, the member dashboard and navigation, email notifications, your own domain, legal texts and inviting your team. A card takes you straight to the right section.
How the menu is organized
The menu on the left groups all sections into four blocks:
- My platform: General, Features, Team & Roles, Login domain, Design, Login, Dashboard, Navigation and Notifications.
- Content: Fields, Tags, Media, Locations and Trash.
- Contract & legal: Billing, Legal, Cookie Banner and Audit Log.
- Integrations & API: Integrations, API, OAuth Apps, Single Sign-On and Custom Codes.
When Payments is on and your role may view payments, a Webhooks entry appears after API. It leads to the webhook page in the payments area.
Features decides which parts your platform offers at all: Community, Courses, Hubs, Events and Payments. A feature that is off disappears from the admin menu, and its entries are removed from the member navigation.
Finding a single setting
You rarely need to know which section holds an option. The search field at the top of the menu, Search: logo, domain, finds sections and individual fields. Pick a field and the section opens, scrolls to it and lets it glow briefly so you see where it is.
On a phone the menu becomes a dropdown with the placeholder Search settings. Below the sections it lists single fields under Jump to setting.
Saving and leaving
Forms such as General and Design do not save as you type. As soon as you change something, a bar appears at the bottom with Unsaved changes, Discard and Save.
If you try to open another page before saving, a dialog asks whether you want to Save or Discard changes first. Closing the browser tab triggers the browser's own warning.
Saved changes to General and Design are written to Audit Log together with the name of the person who made them.
Who can open which part
Settings opens only for roles with the permission Update Platform Settings. Without it, Settings is missing from the admin menu and every settings page is refused. The built-in roles Owner and Admin have it, together with all the permissions listed below. Trainer, Member Manager and Content Manager do not.
Inside Settings, several sections need a second permission before a change goes through:
- Features needs Manage Components.
- Design, including the login pages and the loading screen, and Login need Manage Platform Design. The Community tab under Design is the exception: it saves with Manage Community Settings and only while Community is turned on.
- Navigation needs Manage User Navigation, Dashboard needs Manage Dashboard.
- Tags, Fields, Locations, Trash and Integrations each need their own permission: Manage Tags, Manage Fields, Manage Locations, Manage Trash and Manage Integrations.
- Turning a system email on or off needs Manage Notification Settings.
In the role editor these permissions sit in the Settings group. Names that end in "Settings" are shortened there, so Update Platform Settings is listed as Update Platform.
A custom role can never receive the permissions for roles, team members, API keys or custom code. Team & Roles, API, OAuth Apps, Single Sign-On and Custom Codes therefore stay with Owner and Admin. Roles themselves are managed by the Owner alone.
A few actions are tied to one person rather than to a permission:
- Only the Owner can change, cancel or resume your plan under Billing.
- Only the Owner can create custom roles, and only on a paid plan.
- Delete Platform under General is shown only to the person who created the platform.