---
title: "For IT"
url: https://doorjames.com/solutions/it/
language: en
updated: 2026-09-22
type: solution
section: solution
description: "No second user directory, no servers, no inbound ports: Door James is SaaS with OIDC sign-in, role-based permissions and documented subprocessors."
translations: de=https://doorjames.com/de/loesungen/it/
formats: https://doorjames.com/solutions/it/index.md https://doorjames.com/solutions/it/index.json https://doorjames.com/solutions/it/index.jsonld
bookDemo: https://meet.doorjames.app/public-schedule/99469a6d66d20f7fdd5ee19182a8f8bd (30 min, Microsoft Teams)
---

# Identity, security and operations without extra load

> For IT departments Door James is SaaS without its own user management: sign-in runs through OpenID Connect against your directory, groups drive permissions, and deactivated accounts lose access automatically. No servers, agents or inbound network ports are required; the setup effort sits with app registration and permissions.

What IT actually cares about in workplace software: who creates users, where data sits, what has to be operated – and what effort is left over.

## Key facts

- **Operations:** SaaS, no servers or agents
- **Identity:** OIDC, Entra ID, Graph groups
- **Network:** outbound HTTPS is enough
- **Updates:** roughly every two weeks, no mandatory testing

## The effort sits up front, not in operations

With SaaS, IT effort shifts from operations to integration. For Door James that means concretely: one or two sessions with your identity owner, one app registration, consent for a manageable set of Graph permissions, and a decision about which room resources to synchronize. After that IT responsibility largely ends, because functional administration in the Admin Panel sits with the locations.

## What you need for the security review

For a typical review we provide: an architecture description of the chosen hosting variant, the data processing agreement including subprocessors, the technical and organizational measures appendix, statements on encryption in transit and at rest, a description of the testing approach (OWASP ZAP, CAST, CI/CD) and the role and tenant concept. Where we do not have solid evidence, we say so – for example on the ongoing CIS benchmark implementation or the missing independent accessibility certification.

## Limits you should know early

Door James is public cloud SaaS with logical tenant separation. There is no on-premise operation, and a physically dedicated instance is not the standard model. If your security requirements mandate that, it is a knock-out criterion – and better known in week one than in the steering committee.

## How it works

1. **Connect identity** – OIDC integration with Entra ID or another OIDC provider; groups map onto areas and roles.
2. **Release calendars** – App registration with calendar permissions for the room resources you want to synchronize.
3. **Hand over** – After rollout, location and organization admins manage configuration themselves in the Admin Panel – without a ticket to IT.

## Who it is for

- **Your task during rollout** – App registration in Entra ID, consent for the Graph permissions, release of room resources, optionally deploying the Teams app in the tenant.
- **What you do not operate** – No servers, no database, no client agents, no inbound ports, no separate user accounts.
- **What you should review** – Hosting variant (GCP Frankfurt or IONOS Germany), subprocessors in the data processing agreement, retention periods, role model and CGI access.

## Frequently asked questions

### How many tickets will Door James create for us?

Operations sit with CGI, functional administration with your location owners. For IT, identity topics and the occasional permission case typically remain.

### Can the role model match our governance?

Yes. Roles are granted per organization and location, from a restricted reception role to organization admin, and can be tied to directory groups.

### How do we learn about changes?

Through the release notes, which document every change monthly, and the roadmap for planning.

### What happens in a security incident?

The contractually agreed notification and response paths apply. Internal severity levels and target times are quality goals; binding commitments require a separate agreement.

## Related pages

- [Entra ID & SSO](https://doorjames.com/integrations/entra-id-sso/)
- [Security & hosting](https://doorjames.com/security/)
- [API & third party](https://doorjames.com/integrations/api-and-third-party/)

---
Door James by CGI · https://doorjames.com · doorjames.support@cgi.com