Solution for SaaS IT operations

SaaS IT operations with workspace discovery and tenant subdomains

Let each company use its own workspace while users discover the right portal from their email.

Tenancy
Use company-specific subdomains
Apex domain
Keep Infronest landing only on apex
Sign-in
Send users to the correct workspace before login
Best fit

Who this is for

01

SaaS launch teams

02

Companies with multiple organizations

03

Teams that need web, desktop, and mobile workspace discovery

How it works

  1. 01

    Give every company its own workspace

    Each organization runs on its own subdomain. The Infronest marketing site stays on the apex domain, while tenant subdomains go straight to a company-specific login.

  2. 02

    Let users discover the right portal

    Workspace discovery routes users to their correct workspace from their email address before they log in — the same flow on web, the Electron desktop app and the Capacitor mobile apps.

  3. 03

    Approve who joins

    New tenant sign-ups and access requests route through an owner approval workflow, so growth stays controlled rather than open.

  4. 04

    Set module and role controls per workspace

    Enable modules per tenant and assign role-based access, so every organization gets a footprint sized to its plan and its people.

  5. 05

    Operate with isolation enforced

    Per-tenant reports and activity logs run on top of database row-level security and automated isolation tests, so multi-tenancy is enforced server-side, not just in the UI.

“

A worked example

Take a holding group rolling Infronest out to four subsidiaries totalling 900 users. Each subsidiary gets its own portal on its own subdomain: an employee types their work email on the shared discovery screen and lands on their company’s login, whether they are on the web, the Electron desktop app or the mobile app. New workspace requests wait for owner approval, and each portal’s modules and roles are sized to its plan. Underneath, row-level security keeps the four companies’ records fully separate — enforced in the database, not just hidden by the interface.
Outcomes

What the workflow improves

Use company-specific subdomains

Keep Infronest landing only on apex

Send users to the correct workspace before login

Modules used

Real product areas behind this solution

Workspace selector

Tenant login

Owner approvals

Module controls

RBAC

Yes. Each organization runs on its own subdomain that resolves straight to a company-specific login, while the shared workspace-discovery screen routes each employee to the right portal from their work email address.

Give every company its own front door

Portal-per-company subdomains, email-based workspace discovery and owner-approved joins — with isolation enforced in the database rather than promised by the UI.