Can each company in our building be kept separate?
Rooms and desks, yes — a team space per company, and each company's own directory, make one member's spaces vanish for the others, and their bookings vanish with them. People, no: one account keeps one directory, so everyone stays searchable as an attendee. What a shared room still shows, and where the wall stops.
Partly, and the split is worth knowing before you promise anything to a member company. Spaces can be separated: a room or a desk that belongs to one company does not exist for the others, and neither do the bookings on it. People cannot. One account keeps one directory, so everyone in the building stays searchable as an attendee whoever they work for.
What each company can have of its own
| Its own | What it does |
|---|---|
| Team space | The main one. Put the company’s people in a user group, give that group its spaces, and set Other users to Default — No access to the resources. Those rooms and desks disappear for everyone else. See Give a department its own rooms |
| Directory | Each company can bring its own Microsoft 365 or Google Workspace organisation, with its own sign-in button and its own user synchronisation. See Connect more than one directory |
| Rooms from that directory | A second, automatic wall: where a connection has no Booking agent account, only that directory’s own people can book its rooms — the rest of the building never sees them |
| Administrators | Branch management files each company’s buildings and staff under its own branch, so one company’s administrator never meets another’s configuration |
Why that hides bookings as well
Bookings are never filtered by company — there is no such setting, and looking for one is what makes this question hard to answer. What happens instead is simpler: a booking on a room you cannot see is not there. Separate the spaces and the calendars separate themselves, with no second thing to configure.
Which is also the catch. A room that both companies can book shows both companies’ bookings, with subjects and organiser names, exactly as it would between two departments of one firm. Two settings cover that room, and neither is per-company:
- Private, which the person booking sets on their own booking. See What a private booking hides.
- Hidden booking information on the room’s booking policy, which shows everyone not involved in a booking either nothing or the organiser’s name alone.
Both are judged on whether the viewer was involved in that booking, never on which company they belong to. There is no way to show a booking’s detail to one company and hide it from another.
What every company still shares
- The directory. Everyone in the account is searchable when a booking’s attendees are chosen. There is no setting that limits the people picker to one company.
- Anyone who manages bookings reads every booking in the account, whatever team space it is on.
- Scheduled email reports and the sensor dashboards, which stay account-wide whoever opens them.
- Account, email and audit settings, and the data centre the account lives in.
Where the wall stops
A team space decides what Offision’s own screens show a member of staff. It is built to stop two companies tripping over each other’s rooms, and it does that well — but it is a wall between colleagues, not a contractual boundary between two businesses, and it is worth describing it that way when you sell the space.