UMA Connect. Resource booking across tenants.
Your teams, your sister companies, your guest tenants. All booking the same meeting rooms and workspaces across separate O365 and Google tenants. A capability only on UMA.
One platform. Many tenants.
- 01
One booking surface, many tenants
Sister companies, guest tenants and shared buildings all book against the same pool of rooms, from inside their own directory.
- 02
Each user, their own sign-in
Employees authenticate with the O365 or Google account they already use. No duplicate logins, no shared mailboxes.
- 03
Admins keep control
Each tenant publishes the resources it wants to share. UMA Connect carries that policy. It never overrides it.
Each admin decides what is shared.
Calendars per tenant. Sharing across orgs when you upgrade.
Out of the box every tenant publishes one calendar (Microsoft, Google, or UMA) for its own users. Upgrade to the Calendar Sharing licence and tenants connect multiple calendars at once, with admin-defined permissions for which resources cross the bridge. UMA Connect carries each tenant's policy. It never overrides it.
- Microsoft · Google · UMA
- Single mode · Shared mode
- Per-resource permissions
- No policy overrides
Book from any tenant, from anywhere.
A familiar booking experience, whoever the tenant.
Employees see UMA Connect the way they see UMA: same booking flow, same map, same calendar. The fact that the room they're booking belongs to a different tenant is invisible. The auth, the calendar bridge and the permission policy do the work in the background. Find a desk, book a meeting room, approve a visitor, across any tenant joined to the bridge. From your phone, on the way to the office.
- iOS · Android · Web
- Desks · Rooms · Visitors
- Cross-tenant by default
- Calendar-native
Four estates Connect was built for.
- USE CASE 01 Group structures
Sister companies under one roof
A parent group with two trading companies sharing a London HQ. Each operates on its own O365 tenant. UMA Connect lets both teams book the same rooms without leaving their own directory, and without IT collapsing two tenants into one.
- Holding companies
- Brand portfolios
- Group services
- USE CASE 02 Mergers & acquisitions
Day one of integration
Two tenants, one estate, no time. Connect bridges the calendar and auth layer on day one, buying IT the runway to plan a deeper consolidation without forcing either side to migrate first.
- M&A integration
- Tenant-to-tenant
- No forced migration
- USE CASE 03 Shared buildings
Landlords with multiple occupiers
A serviced building with several tenant companies. The landlord publishes floors, rooms and amenities. Each occupier gets controlled, policy-aware access, booked from inside their own Microsoft or Google identity.
- Serviced offices
- Workspace operators
- Floor-by-floor leasing
- USE CASE 04 Alliances & JVs
NHS alliances and joint ventures
Trusts working under an alliance, or partners running a joint project, sharing clinical and admin space across organisations. Each side keeps its own policy and identity provider. Connect carries the booking across the bridge.
- NHS alliances
- Project JVs
- Cross-org clinics