Sign in with Google – available
Google is one of the preconfigured OpenID Connect strategies. People use their Workspace account, and Door James never becomes a second place where passwords live.
Integrations
Google Workspace: sign-in today, calendar as a pilot
Most workplace tools are built Microsoft-first. This page says plainly which parts of Google Workspace work today and which are a pilot conversation.
In short
Door James supports Google Workspace sign-in today: Google is a preconfigured OpenID Connect strategy, so people use their existing Workspace account and no second password exists. Usage data can be exported into Looker Studio. Calendar and room synchronization with Google Calendar exists as a proof of concept, not as a shipped feature, and is available as a pilot.
- Sign-in
- available – Google as a preconfigured OIDC provider
- Reporting
- available – export into Looker Studio
- Calendar and rooms
- proof of concept, pilot on request
- Honest summary
- identity yes, calendar not yet
What works today, and what does not yet
No separate user list – available
Because identity comes from Workspace, a deactivated account loses access to Door James without anyone maintaining a second list.
Reporting into Looker Studio – available
Occupancy and booking data can be exported and read in Looker Studio, formerly Google Data Studio, next to your other dashboards.
Everything else in the product – available
Desk booking, visitor management, events, evacuation, analytics and the apps do not care which suite you run. Only the calendar side is Microsoft-specific today.
Google Calendar rooms – proof of concept
Two-way room calendar synchronization, the equivalent of what the Outlook integration does, exists as a working proof of concept rather than a shipped feature. We show it, we do not sell it as available.
Pilot instead of a promise
If Google Calendar rooms decide your project, the honest route is a pilot with a scope and a date, agreed before the contract – not a tick in a requirements list.
Why this page exists
Door James grew up in Microsoft environments, and it shows: rooms synchronize through Graph, there is an Outlook add-in and a Teams app. Organizations on Google Workspace reasonably ask what that means for them, and the answer is neither "everything works" nor "nothing works".
Sign-in works today, and that is the part that usually decides whether IT will look at a tool at all: Google is a preconfigured OpenID Connect provider, so nobody creates a second account and a leaver loses access through the directory. Reporting works too, through export into Looker Studio.
The one piece that is missing
Two-way room calendar synchronization with Google Calendar is a proof of concept. It runs in a demonstration; it is not a feature you can switch on, and it is not covered by support.
We could have listed it as available. Written down, that sentence survives exactly until the first pilot, and then it costs more than it won – the trust, usually, rather than the deal. So it stands here as what it is, and the useful next step is a pilot with a scope and a date rather than a tick in a matrix.
What to do with that
If your rooms live in Google Calendar and that link is decisive, raise it before the contract. A named customer with a real requirement is what turns a proof of concept into planned work, and the conversation is a lot easier in a project plan than in a complaint.
If rooms are a smaller part of the picture – desk booking, visitors, events, occupancy figures – then Google Workspace is not a limitation today, and the sign-in side is already where it should be.
Who it is for
For IT in a Google organization
Sign-in and user lifecycle work today through OIDC. The calendar question is the one to raise early.
For procurement
A written distinction between available and pilot, so the requirement matrix is filled in correctly the first time.
For mixed environments
Organizations running both suites use Microsoft for rooms and Google for sign-in without a conflict.
Frequently asked questions
Can we use Door James with Google Workspace today?
Yes, for everything except room calendar synchronization. Sign-in runs through Google as a preconfigured OpenID Connect provider, and desk booking, visitor management, events, evacuation management and analytics are independent of the office suite. What is not available yet is the two-way link between Door James and Google Calendar room resources.
Is the Google Calendar integration available?
No. It exists as a proof of concept – it works in a demonstration, it is not a shipped, supported feature. We would rather write that here than have you discover it during a pilot. If it is on your requirement list, bring it into the conversation before the contract so it can become a scoped project item with a date.
What is the difference to the Microsoft integration?
On the Microsoft side, room calendars synchronize in both directions through Graph, there is an Outlook add-in and a Teams app. On the Google side, sign-in and reporting are there today; the calendar equivalent is the piece that is missing. That asymmetry is a consequence of where the demand came from first, not a product decision against Google.
Can we book meeting rooms at all without the calendar integration?
Yes. Meeting rooms are bookable in Door James itself, with rules, equipment filters and displays. What the integration adds is that a booking made in Google Calendar also blocks the room in Door James and the other way round. Without it, one of the two systems has to be the single place where rooms are booked.
When will it be available?
We do not have a date, which is why none is written here. A pilot creates one: with a named scope and a customer who needs it, it becomes a planned piece of work instead of an item on a wish list.
Help Center
Bring your actual setup to the call
Which tenant, which directory, which calendars, which identity provider. Thirty minutes is enough to say whether it fits – and where it will not.