Enterprise
Roll out on the foundation you already have.
Enterprise deployment is a path for organizations that need administration, integration, and oversight around the same standard experience. It is not a second product, and it is not a barrier to reading the standard plan.
Start with the people who will use it.
Existing Ciright users sign in with Keyra. Their subscriptions, permissions, and application ownership stay where they are. A new marketing page does not migrate a subscription or create a duplicate World.
Connect remains administration.
Users, teams, roles, applications, and permissions are administered in Connect. ADM does not keep a separate permission master. Paid-seat changes, when billing is connected, belong to authorized administrators and should show the consequence before confirmation. That billing action is not available on this website.
Governance
Identity, scoped access, approval policy, action limits, and activity records are how AI stays inside the business. Agents do not approve their own sensitive actions or grant themselves tools. Security describes what this repository actually implements and what it does not certify.
Integrations
External systems connect through the existing ESID relationship, with the provider, subscription, and object in context. Email domains are not a substitute for membership. A public connector catalog, with prices and logos, is not published here.
Deployment options
This repository documents the ADM web experience and the Keyra sign-in handoff. It does not publish a regional deployment matrix, a private-cloud offer, or a services price. Those options stay unpublished until they are approved.
The demo form does not confirm a meeting until a request service accepts it.