Frequently asked questions about Door James

As a planning assumption, around four weeks for the first location; further locations can be rolled out in parallel. Actual speed depends heavily on how quickly floor plans, asset lists and identity coordination arrive from your side.

Project and location owners, floor plans, the list of bookable assets, office metadata, coordination with your IT on identity and Microsoft permissions, privacy input, internal user communication and approval of the configured locations.

Typically kick-off and demo, alignment on module scope, SSO setup, collection of floor plans and assets, configuration of privacy and visitor settings, integrations, approval by location managers, optional sticker order, admin training, user communication and go-live.

Not for the standard rollout. Custom development, bespoke documentation or consulting can require a separate agreement.

Yes, location by location. The only constraint is the commercial minimum of 250 authorized users.

Through Entra ID for single sign-on using OpenID Connect, Microsoft Graph for profile and group data, Exchange Online for bidirectional room calendar synchronization, and a Teams app for booking and notifications.

No. Microsoft is the most common case, but Door James speaks OpenID Connect generically; Google is preconfigured and other OIDC providers can be configured.

SAML is in development or under discussion but is not represented as a production standard while the current status is unconfirmed.

Door James can address third-party systems through common standards. Whether a specific locking system can be connected depends on the vendor and is verified before any commitment.

No. Outbound HTTPS is sufficient; no special inbound ports are required.

In the standard variant the application is hosted in the Google Cloud region Frankfurt, with email and database services involving further subprocessors. For requirements of exclusively German processing there is the IONOS variant, whose agreement lists hosting, email and database in Germany with no third-country transfer.

First name, last name, email address, the identifier of the booked resource, booking time, check-in and check-out time and the IP address. Activated modules can add more.

You decide. Anonymization and deletion periods are configurable and can differ for booking data, visitor data and problem reports.

Your organization is usually the controller and CGI processes the data as processor under a data processing agreement. Legal basis, privacy notices and retention configuration remain with you.

No. Geofencing is optional, requires explicit permission for location services and is evaluated locally on the device. No permanent location history is stored for it.

EUR 2 per authorized user per month in the euro markets with a minimum of 250 users. In the United States USD 2 and in Canada CAD 3 per user per month.

Yes. Door James is not licensed module by module; the standard capability stack is part of the subscription.

Discounts are not the default and are typically discussed only at materially larger volumes, around 5,000 users and above.

The German standard form provides for twelve months initial term with twelve-month renewals. Negotiated and public-sector contracts can differ.

Introducing an application that processes booking and presence data regularly touches codetermination rules. We support with technical information on data types, evaluations and configuration options; the legal assessment and the agreement itself sit with your organization.

Evaluations target spaces and resources. Configurable anonymization periods additionally define when personal references are removed.

In our experience: clearly naming the data types processed, the purpose limitation, retention and anonymization periods, the roles with access, and the voluntary nature of optional features such as geofencing and the colleague finder.

No. The web app provides full functionality in the browser. Native apps make sense for push, QR check-in and geofencing.

Nine: English, German, French, French (Canada), Dutch, Spanish, Italian, Portuguese and Finnish.

The documentation describes 24/7 ticket support with access from the Member App and Admin Panel as well as through help.doorjames.com, complemented by a knowledge base and tutorials. Ticket support is documented in English and French; tutorial content in German, English and French.

The internally documented times are quality targets, not contractually assured SLAs. Binding response or restoration commitments require a separate written agreement.

Door James 2.0 has been designed against relevant BITV/WCAG criteria. An independent certification has not been completed, and we do not claim one.