What it does
Organization settings hold the config that applies to every institution in your account: identity, regional defaults, security policies, academic period rules, and the shared lists used to classify clinical sites. Settings are grouped into three sections: General, Policies, and Sites.
Who it's for
Organization administrators — only organization admins can save changes, while other org-portal users see the settings read-only with a notice that an organization admin must make edits.
How it works
General sets the organization's name, short name, and website domain, plus regional defaults: timezone, date format, and platform language. An Appearance card holds the org's primary and secondary brand colors.
Policies sets security defaults: password policy, session timeout, and whether multi-factor login is required. This section also holds the Allow custom periods switch, which decides whether institutions and programs can create their own academic periods or must use only the org-managed ones.
Sites is a three-tab area for the lists every clinical site uses: Site Types, Relationships, and Regions & Hubs. System entries are shared across the platform. Institution-specific entries can be added alongside them. When both exist for the same code, the institution-specific one wins.
Before you start
You need to be an organization admin to save changes here. Other roles see the same pages read-only.
Do this
Open the
/organization/settings/generalpage → the General section loads with Identity, Regional, and Appearance cards.Check the top-right of the page for a Save button → if it's missing, you're on a read-only view and need an organization admin to make the change.
Update fields such as Organization Name, Short Name, Domain, Timezone, Date Format, or Language in the Identity card → each field keeps your typed value.
Select the Save button → expect a "Settings saved successfully" toast, and the fields keep your new values.
For security or academic period rules, open the
/organization/settings/policiespage instead → confirms the same Save flow works there.
You're done when
✓ A "Settings saved successfully" toast appears after you select Save.
✓ The field you changed still shows your new value after a page refresh.
✓ Institutions and programs can (or can't) create their own academic periods, matching your Allow custom periods choice.
Boundaries and limits
Only organization admins can edit. Everyone else in the org portal is read-only.
You can't upload an organization-level logo yet — the upload buttons show but are disabled. Upload logos on each institution instead.
The page states that API and SSO integrations will arrive in a future release. They are not configurable here yet.
Site types, relationships, and geographic zones can't be hard-deleted. Removal is a soft archive, so historical site data keeps its classification.
Turning off Allow custom periods limits institutions and programs to org-level periods. It does not delete periods they already created.
Common questions
Q: I can see settings but the Save button is missing. Why? A: You are not an organization admin. Settings render read-only for everyone else — ask an organization admin to make the change.
Q: Does changing the organization language change it for every user? A: It sets the org default. Regional settings resolve in layers, so a more specific context can still differ.
Q: Can I delete a site type we no longer use? A: You can archive it so it stops appearing in pickers. It is never hard-deleted — sites that already carry it keep their history.
Q: Where do I upload our logo? A: Organization-level logo upload isn't available yet. Upload logos on each institution from its Branding tab.
Related articles