Appearance
Olympus Backend: Multi-tenancy & Orchestration
Purpose: The central layer that keeps every operator's data separate, handles staff sign-in, and coordinates the other applications. Most people never touch it directly, but it's what makes the ecosystem hang together.
Primary users: Platform administrators and back-office staff, plus the other apps and partner systems that talk to it behind the scenes.
See it live: no screen of its own; it's the API behind the other apps. See Accessing the systems.
Think of Olympus Backend as the identity and traffic-control hub. It decides who you are, which operator you're working in, what you're allowed to do, and hands you off into the right app.
Multi-tenancy
What it does: Keeps each operator's data completely separate and works out which operator a request belongs to.
Who uses it: Everything, it underpins the whole platform.
Key rules:
- Each operator is a separate tenant with its own isolated data, so one operator's data can't bleed into another's.
- The operator is identified by the web address being used. Central (platform-wide) addresses are handled separately from operator-specific ones, and operator URLs can't be reached on the central address.
- For system-to-system calls, a header names which operator's context to work in.
Sign-in & authentication
What it does: Authenticates staff, using AWS Cognito or Microsoft (Azure AD) single sign-on, and issues an access token scoped to the app the user is entering.
Who uses it: All internal staff, and partner systems (which authenticate as an operator).
Key rules:
- Handles the "set a new password" step on first login, and the full password-reset flow.
- A token carries the user's abilities for the specific app they've signed into, so access is contained to what they need.
Users, roles & permissions
What it does: The platform-wide model for accounts, the roles that group permissions, and the permission catalogue.
Who uses it: Administrators.
Key rules:
- You can't edit or delete your own account, and only a super admin can change another super admin.
- Supports searching, scoping to one operator, and (for super admins only) an "all operators" view.
- Includes CSV export, sending a temporary password, and managing a user's reporting (Tableau) access.
Companies, systems & integrations registry
What it does: The master list of operators, the apps that make up the ecosystem, and the third-party integrations available to each operator.
Who uses it: Administrators.
Key areas:
- Companies: create and configure operators. Deleting an operator isn't available by design.
- Systems registry: the catalogue of apps (Everest, Portal, reporting, and Olympus itself), which drives the launchpad. This is what powers the hand-off that sends a user from the launchpad straight into another app, already signed in.
- Integrations catalogue: the list of connectable systems (HubSpot, Rent Profile, Reposit, Rightmove, Zoopla, On The Market, Inventory Hive, smart locks, Storyblok, and a student-specific one). Each can be configured per operator, toggled on or off, and switched globally by a super admin. Operators can also mint and revoke integration access tokens for partner systems that call in.
- Per-operator configuration also covers AI settings, mail templates, support configurations, and the launchpad's partner and content links.
Integration proxies (HubSpot, Rent Profile)
What it does: Lets the other apps and partner systems reach HubSpot and Rent Profile through Olympus, using each operator's own stored credentials, so those credentials never have to be spread around.
Who uses it: Partner systems and internal apps, authenticating as an operator.
Key rules: The caller authenticates as an operator, and Olympus proxies the request to the third party on that operator's behalf. HubSpot covers CRM records and pipelines; Rent Profile covers creating tenancy records and checking tenancy status.
Property & unit data
What it does: Manage an operator's properties and units against that operator's own database.
Who uses it: Administrators and the other apps, working in a specific operator's context.
Reporting
What it does: The backend behind the Tableau reporting seen in Olympus Frontend, projects, workbooks, views, and the per-user Tableau credentials. Admins can also manage report help content (guidance attached to workbooks) and see Tableau licence-usage statistics.
Who uses it: Users with reporting access.
Key rules: Access is checked against both platform permissions and report ownership.
Integrations used by Olympus Backend
| System | What it's used for |
|---|---|
| AWS Cognito / Microsoft (Azure AD) | Staff sign-in |
| HubSpot | CRM records and pipelines (proxied per operator) |
| Rent Profile | Tenancy records and status checks (proxied per operator) |
| Tableau | Reporting |
Related documentation
- Move-in Tracker API, v3 Endpoints
- Coding Standards & Architecture Review (internal)