Organisation Settings
Settings for one organisation live at /organisations/[id]/settings, reachable from the Settings link beside any organisation you administer on the organisations screen.
Only an administrator of that organisation can open it. A non-admin member sees “Only an administrator of <name> can manage its settings”; a non-member gets a plain “not found”. The app does not distinguish an organisation you cannot see from one that does not exist.
The page works on the organisation named in its own URL rather than the one you currently have selected, so an admin of several can manage any of them without switching first.
The page has these sections, in order:
General
- Name: the clinic’s display name, shown in the switcher, on the organisations list, and anywhere the organisation is named.
- Slug: its short identifier, unique across Medbot.
- Country: decides which integrations are available.
- Time zone: the organisation’s local time zone.
- Active / Inactive: shown as a badge. An inactive organisation is not selectable and its members cannot act in it.
Save changes applies all four fields together and is disabled until something actually changes.
A Singapore organisation with SmartCMS modules cannot change its country until the modules are cleared: “Clear the SmartCMS modules under Integrations before changing the country.”
Integrations
Country-specific national services, at #integrations.
- Singapore: the card is titled Singapore integrations: “The SmartCMS services this clinic uses. Each one also needs Synapxe’s approval for every location before it connects.” Pick modules in the module picker (or Use GP starter) and click Save integrations. See Modules & Gating.
Once at least one module is saved, a SmartCMS settings button opens the organisation’s SmartCMS tab (
/organisations/[id]/smartcms). There an admin switches services on per location, tests the connection and exports the Synapxe onboarding rows. Only an administrator can open it. See SmartCMS Settings. - Anywhere else: “No country-specific integrations are available for <country>.”
Singapore registration
Singapore organisations only, at #registration: the organisation’s UEN and GST registration, saved with Save registration, and the details of each clinic location.
Under Clinic locations, one location is shown at a time. If the organisation has more than one, choose it from the Clinic dropdown. The choice is kept in the page address as ?location=<id>, so a link can open a given clinic, for example the Edit codes link on the SmartCMS tab. Unsaved edits survive switching between clinics.
Each location has its HE code, Hospital Code, Contact email and Contact phone, saved together with its own Save. Replacing an HE code or Hospital Code that is already set asks for confirmation first, because it switches SmartCMS services at that location off. The dialog is titled, for example, “Change the HE code of Main Clinic?” and its button is Change the code. Setting a code for the first time needs no confirmation.
See Singapore Registration for the formats and what to do after changing a code.
Join code
The short code an admin hands to a new hire so they can request access before being invited by email. The section shows the current code with a Copy button.
Regenerate join code issues a new one. The previous code stops working immediately; use it if a code has been shared too widely or has leaked. Regenerating does not affect anyone who has already joined.
The full flow around this code is described in Join an Organisation.
Seed data
“Add staff and patients in bulk from a CSV file. Safe to repeat: people who already exist are skipped.” Seed staff & patients opens the seeding page. See Seeding Staff & Patients.
Medplum credentials
Managing the organisation’s connection to its own Medplum server. This section has its own page: Medplum Credentials. For a Medbot-hosted organisation it only shows the base URL and a Verify connection button, because Medbot manages the credentials.
A note on enforcement
Every action on this page is re-checked server-side against your membership and role in that specific organisation, independently of anything the page itself decided. The page’s gating is there to show you a helpful message, not to be the security boundary.
The API also accepts only the fields each action declares. A request that tries to slip in anything else, such as a join code on a general update or a role on a user profile, is rejected outright rather than silently applied.