Human, service & system principals
Represent people, integrations and internal system actors explicitly rather than sharing credentials.
Trust Center
Security, access and operational responsibility by design.
XTND is built around scoped identity, explicit context, auditable privileged access and configurable deployment choices. This page explains the architecture and the commitments that should be verified per deployment.
Identity & access
Know who is acting, where they are acting and what they are allowed to do.
XTND distinguishes principal identity from active context. Memberships, roles, direct grants and scope combine into effective access for the current business or client environment.
Scoped membership
Access follows organization, workspace and delegated relationships instead of a single global admin flag.
Context switching
Move between authorized contexts without pretending to be another user.
Data & deployment
Choose the deployment model appropriate to the operating responsibility.
XTND supports shared, isolated and dedicated deployment patterns through its infrastructure layer. Encryption, data residency, backups, retention, recovery objectives and SLA commitments are specified for the selected deployment.
Deployment choice
Match shared, isolated or dedicated infrastructure to the business and compliance requirement.
Data scope
Keep tenant and workspace boundaries explicit in application and data access paths.
Recovery planning
Backups, DR and recovery objectives belong in the operating contract, not only in application code.
Audit & privileged access
High privilege should leave evidence.
Privileged support and impersonation paths are explicit and auditable. Actions remain tied to the real acting principal, active context and granted scope.
Actor
Context
Granted scope
Action
Audit event
Review
Responsible AI operations
Treat models and agents as governed platform resources.
Budgets, provider routing, tool scopes, usage logs, human approvals and fallback policies help keep AI aligned with the risk of the workflow.
Budgets
Control consumption at tenant, user, module or capability level where supported.
Tool permissions
Limit which actions and external systems an AI workflow can access.
Human approval
Keep people in the loop for financial, legal, operational or otherwise consequential decisions.
Operational transparency
Confirm the controls that apply to your deployment.
For production deployments, the applicable security and operations specification defines the controls that apply to that environment, including backup, retention, recovery, data residency and support commitments.
CMS and Website Builder releases are validated with automated regression, scoped authorization tests, database-backed certification, migration/rollback checks and lifecycle failure testing. Final environment acceptance remains deployment-specific.