Security & access

Practical controls for enterprise deployments.

Crenex supports portfolio access, user roles and configured integrations without separating operational governance from the booking workflow.

Crenex OS
Crenex OS enterprise controls overview
Admin ConsoleRoles and permissions catalogue for enterprise teams

Deployment controls

The facts that matter during review.

The final security, hosting and integration scope is documented for the customer’s deployment and geography.

Roles & permissions

Configure access around the users, assets and operational responsibilities in the deployment.

Single sign-on

SSO requirements, including Azure or Okta environments, can be assessed as part of implementation.

Activity context

Keep booking, agreement, message and transaction activity attached to the operational record.

Data protection

Crenex positions the service as GDPR-first; contractual and privacy requirements are confirmed during review.

Hosting & residency

Hosting region and data-residency requirements are confirmed for the customer’s geography and service scope.

Integration review

Authentication, data direction, field scope and error handling are agreed for each connected system.

AI module

Scope access before enabling assistance.

AI functionality should be introduced with a defined data set, use case and review process.

Data scopeChoose the Crenex data and approved documents available to the module.
User accessAlign access with the permissions and deployment configuration.
Human reviewRequire people to review outputs before external or operational use.
Use-case rolloutTest a bounded question or drafting workflow before expanding the scope.

Technical review

Security answers should match the contract and deployment.

Crenex can provide the documents and answers relevant to procurement, IT and privacy review for the proposed service scope.

Certification, encryption and hosting details are stated only when they are supported by the approved service documentation for that deployment.

ArchitectureService scope, environments, integrations and data flows.
AccessUser lifecycle, roles, SSO and administrative responsibilities.
PrivacyData categories, retention, locations and contractual requirements.
OperationsSupport, incident handling, continuity and customer responsibilities.