Appearance
Olympus Frontend: Admin Console & Reporting
Purpose: The central admin console for the platform, the single sign-on launchpad into the other apps, and the home of Tableau reporting.
Primary users: Platform administrators and, for the launchpad and reports, every internal user.
See it live: this is the launchpad itself, olympustech.ai. See Accessing the systems.
Olympus Frontend has two halves: an admin console (companies, users, roles, permissions, properties, units) and a user launchpad and reporting portal (the post-login home, bookmarks, and embedded Tableau dashboards).
Sign-in
What it does: Lets users log in two ways, Microsoft (Azure AD) single sign-on, or email and password. It also handles password recovery and the first-login temporary-password flow.
Who uses it: Every user. Microsoft SSO is the main route; email/password is the fallback.
Key rules:
- Single sign-on is the primary path; individual accounts can carry a "bypass SSO" flag to use email/password instead.
- Sessions refresh in the background (about every five minutes); an expired or missing session sends the user back to the login screen.
Roles, permissions & page access
What it does: Controls who can see and do what across the console. Every admin page is gated by the user's role and specific permissions.
Who uses it: Enforced for all users; the console pages are effectively admin-only.
Key rules:
- A super admin bypasses all checks.
- Each page declares the roles and permissions it needs (for example, company AI settings need the "manage AI settings" permission). Access is checked on both the server and the browser, so a link that shouldn't be visible also can't be reached directly.
- Being denied a page returns the user to their home screen with a notice.
Home / SSO launchpad
What it does: The screen a user lands on after login. It presents the apps they can access (Portal, Everest, reporting) as tiles, plus two sets of quick links, content-management links and partner-system links.
Who uses it: Every logged-in user; the tiles shown depend on the systems and permissions they've been granted.
Key rules:
- Clicking an app tile hands the user off into that app with an authenticated deep link, so they don't log in again.
- Content-management and partner links open in a new tab.
Company administration
What it does: Manage each operator (the platform tenant, shown as a "company") and its settings. Beyond basic details, this is where per-operator configuration lives.
Who uses it: Administrators.
Key areas:
- AI settings: set an operator's brand tone and shared property information, which shape AI-generated content elsewhere.
- Integrations: enable and configure an operator's third-party connections (Qube, Reposit, Inventory Hive and others).
- Mail templates: edit an operator's email templates (subject, HTML and text) from a set of allowed variables, including the Section 13 rent-notice family.
- Tenant support configurations: set up how residents get support, choosing from four methods (free-text email, a HubSpot form, an app rating/feedback flow, or a redirect to a maintenance page), each toggleable and drag-to-reorder.
Users, roles & permissions
What it does: Full management of user accounts, the roles that bundle permissions, and the permission catalogue those roles are built from.
Who uses it: Administrators.
Key capabilities:
- Create and edit users; send a user a temporary password; export users to CSV; assign a user to Tableau groups for reporting access.
- Roles are system-scoped, and the canonical set (super admin, admin, property manager, lease officer, concierge, and others) determines what's valid in each app.
Properties & units
What it does: An administrative view of the estate, creating and editing properties and the units within them.
Who uses it: Administrators and property managers, who can hold permissions scoped to specific properties.
Bookmarks
What it does: Personal saved links, so a user can jump back to any page in one click.
Who uses it: Every logged-in user, individually.
Key rules: Bookmarks are drag-to-reorder, and any page can be bookmarked or un-bookmarked on the spot.
Reports (Tableau)
What it does: A drill-down into the business-intelligence dashboards, Projects → Workbooks → Views, with the chosen view embedded live from Tableau.
Who uses it: Users granted reporting access.
Key rules:
- The report menu is pre-loaded on entry so navigation is always populated.
- Each user needs their own valid Tableau credentials to see the embeds; the app checks and refreshes these, and admins can grant a user "Insights & Reporting" access from the user screen.
Integrations used by Olympus Frontend
| System | What it's used for |
|---|---|
| Microsoft / Azure AD | Single sign-on for staff |
| Tableau | Embedded reporting dashboards |
Related documentation
- Single Sign-On (SSO)
- Insights & Reporting Enhancements, Feature test plans
- Tableau integration (repo doc)