1
Provision tenants in the super-admin
List your subsidiaries, pick subdomain slugs, set per-tenant logos and feature flags. New tenants are spun up in under five minutes from the admin console.
Enterprise Solution
One platform. Many subsidiaries.
What is multi-tenant architecture in WORKSPHR?
A single deployment of WORKSPHR that hosts independent organizations under their own subdomains, with row-level data isolation, per-tenant branding and feature flags, and a super-admin console that can spin up or wind down a subsidiary without engineering involvement. Built on AWS ap-southeast-1 for data residency.
Holding companies, conglomerates, and BPO groups in PH typically run 4 to 12 separate HR systems across subsidiaries. WORKSPHR collapses that into one billing account, one super-admin console, and one set of compliance updates that propagate everywhere.
Why running 6 HR systems doesn't scale
Every subsidiary on a different tool means 6 vendor contracts, 6 admin trainings, 6 BIR alphalist exports to consolidate, and zero visibility for the parent CFO. Multi-tenant architecture is the structural fix, not just a discount.
Vendor sprawl
Different tool per subsidiary, no shared config
Compliance drift
Sub A on 2024 BIR, Sub B still on 2022 brackets
Cross-tenant leak risk
Excel exports merged manually, mistakes in HR copies
Group reporting blind
Parent CFO has no rolled-up headcount or comp view
Enterprise architecture, ready to ship.
Subdomain routing, database isolation, super-admin console, per-tenant feature flags, AWS deployment topology, the same architecture WORKSPHR uses for itself, made available to your group.
Every subsidiary gets a subdomain matching its slug, e.g. acme-corp.worksphr.com. The TenantMiddleware reads the Host header on every request, resolves the org, and scopes the session, with no app-level branching needed.
- Per-subsidiary subdomain (acme-corp.worksphr.com)
- Reserved: admin · app · staging · api
- Per-tenant logo, colour, email-from
- End-users never see the parent brand
From contract to first payroll, group-wide.
2
Migrate or import per subsidiary
Each tenant gets its own employee import, payroll history, and 201 file load. WORKSPHR Implementation Specialist runs in parallel across all subs.
3
One bill, one update cycle
BIR/SSS/PhilHealth changes propagate to every tenant on the next deployment, no per-sub upgrade contract. The parent CFO sees consolidated headcount and comp on a single dashboard.
Is each subsidiary's data really isolated?
Yes. Every tenant carries anorg_id. The TenantMixin and repository base class auto-injectWHERE org_id = :org_idon every query. CI tests include cross-tenant leakage checks that block merges if the filter is missing. We use shared schema with row-level tenancy so backups, migrations, and PITR cover everyone in one operation, but no tenant can read another tenant's rows.Can each subsidiary have its own branding and subdomain?
Yes. Every organization gets a subdomain matching its slug, e.g.acme-corp.worksphr.com. Logo, color tokens, email-from address, and workflow defaults are configured per tenant. End-users never see the parent brand unless the parent chooses to surface it.Can I run different feature flags per subsidiary?
Yes. The four-tier guard chain(Subscription → SDO → RBAC → Department) enforces feature gating at the route level. The super admin can enable Surveys for the BPO subsidiary, disable Performance Management for the manufacturing one, and the sidebar nav for each tenant updates accordingly with no code change.What region is the data hosted in?
Asia Pacific (Singapore) — AWSap-southeast-1. Aurora PostgreSQL Multi-AZ for the database, ElastiCache Redis for sessions and rate limits, S3 for uploads (logos, resumes, payslips, reports), CloudFront + WAF in front. Data residency disclosure available on request for your DPA filing.Can a single sign-on cross subsidiaries?
Yes for super-admin and shared-services users. They can switch tenant context from a single login. Regular employees stay scoped to their employing entity unless explicitly granted access to a sister org by the super admin. Audit logs record every cross-tenant context switch for compliance. Contact us for SSO setup details.
Run every subsidiary on one platform.
Book a 30-minute demo with our enterprise team. We'll walk you through tenant provisioning, isolation guarantees, and AWS topology, live.