AI Workspace
Secure enterprise AI access through the existing POLICYMUX workspace.
POLICYMUX PLATFORM
Govern and access enterprise AI applications through one secure platform.
CURRENT CONTEXT
Access the POLICYMUX capabilities available to your organization.
Secure enterprise AI access through the existing POLICYMUX workspace.
Durable governed memory capabilities powered by the JRAI platform.
Manage POLICYMUX applications and customer access from one control plane.
Future organization, access, policy, domain, and platform administration.
POLICYMUX is backed by the JRAI governance and platform services already deployed in Azure DEV.
Microsoft-authenticated POLICYMUX workspace access.
Central routing, model, provider, tenant, and application controls.
Phase 9 memory services are deployed in the JRAI DEV platform.
Keep Memory, and later Knowledge, separated by the work or subject they belong to.
Knowledge sources, secure ingestion, lifecycle, replacement, and retrieval readiness are managed through RAG for the active Project.
Opening a Project changes the active Memory context. Archived Projects remain preserved.
Review governed files available in your authorized Projects and Chats, including lifecycle and security state.
This view combines expiring or grace-period files with persisted failed upload sessions visible to your authorized context.
Review Skills available through your current POLICYMUX authorization, including scope, lifecycle, and revision.
View and manage the durable information POLICYMUX may use as context in future AI conversations.
Choose a saved memory to review its content, scope, lifecycle, and permitted management actions.
Governed Knowledge and retrieval for your active Project.
Add source material to the active Project through the governed POLICYMUX Knowledge ingestion boundary.
Review the sources available to the active Project and their governed retrieval state.
No active Projects are available to your authenticated context.
View the applications and domains available to your authenticated POLICYMUX tenant.
Application and domain information is loaded directly from JRAI.
Browse governed POLICYMUX Help or open guidance for the product area you were using.
Ask about POLICYMUX. Answers use only Help you are authorized to read.
Create and manage governed Help revisions. Publication and lifecycle actions remain authorization-controlled and audited by POLICYMUX.
Select capabilities relevant to this article. Readers need effective access to at least one selected capability. No selection means generally available Help. Relevance is saved with the draft and published revision.
Manage POLICYMUX companies, tenant environments, and platform administration settings.
Customer ownership boundaries available to this platform administrator.
Choose a company to view its platform identity and tenant environments.
Manage customer users across POLICYMUX Companies. Company transfer is available to platform administrators. Detailed role administration will be added separately.
Govern POLICYMUX Access Profiles, capabilities, and role mappings.
Govern restricted AI topics across Platform, Company, Tenant, and Workspace scopes.
Platform policies apply across POLICYMUX and are inherited by lower administration scopes while active.
Govern sensitive information handling across Platform, Company, Tenant, and Workspace scopes.
Platform Data Protection establishes the POLICYMUX-wide baseline inherited by all lower scopes.
Govern JRAI Auto model selection and user override behavior across Platform, Company, Tenant, Organization, Workspace, and Project scopes.
Platform Routing Policy establishes the POLICYMUX-wide JRAI Auto and model-override baseline inherited by lower administration scopes.
Create, review, govern, and evaluate enterprise Memory at Company, Tenant, Workspace, and Project scope.
Select an authorized governance scope.
Govern Provider connections, Provider and Model configuration, operational health, lifecycle, cost visibility, and effective governed availability.
Select an authorized Provider administration scope.
Review the configured and applied POLICYMUX runtime profile, modeled cost and service implications, and request a governed profile activation.
Manage infrastructure, application systems and customer entry points. Governed execution has its own readiness and approval requirements.
Registration creates a management record. Azure ownership and application installation are verified separately.
Existing Azure candidates below are onboarding shortcuts. Manage every registered Shared or Dedicated TEST/PROD instance in the inventory.
Loading existing infrastructure candidates…
Loading registered infrastructure…
Choose an instance to manage its systems and customer assignments.
Select infrastructure to inspect its allocation.
Select an available existing candidate to reuse its foundation. Registered instances remain selectable in the inventory. No Azure resource IDs are needed.
Select an infrastructure in the overview first.
Application systems appear after you select infrastructure.
Registering a system does not deploy an application or assign a release. Deployment is managed in Provisioning & deployment.
Select an infrastructure and application system first.
Select a company and tenant to inspect its environment contexts.
Enter the approved business or technical reason. Dedicated TEST remains optional; this does not create infrastructure or enable access.
This registers a logical tenant context only. It does not enable TEST access, provision resources or deploy an application.
The tenant needs a matching environment and hosting assignment. Dedicated infrastructure accepts only its owner's tenants. Assignment does not grant membership or TEST access.
Multiple customer URLs can use the same Shared application system. A customer-specific hostname does not require another deployment.
Select an active customer assignment and application to inspect its URL permissions.
Application URL permissions are separate from Shared/Dedicated infrastructure hosting. An explicit authorized change affects this tenant application wherever it is used. It does not grant TEST access, change hosting, verify DNS or activate a URL.
Registration and association do not configure DNS or establish live TLS readiness.
Select an infrastructure, system and authorized customer context to inspect its worker readiness.
Private publication requires its approved publisher, registry connection and release.
Infrastructure provisioning uses its approved allocation. Select customers separately for application deployment and access.
A trusted worker and fresh readiness evidence are required. An authorized administrator approves the exact saved plan before execution.
Shared-pool deployments affect all customers assigned to that system. Context registration does not grant TEST access or provision resources.
Publish only an approved immutable release through the configured private publisher. No rebuild or public-network fallback is implied.
Approvals, recorded plan details, progress and recovery actions appear here when operations exist.
Actions use the infrastructure, system and customer assignment selected above. Available actions remain subject to current server-side authorization and evidence.
Shared actions preserve neighboring customers. Suspension, archive, restore and activation are distinct operations. Deletion remains unavailable until its policy and execution controls are accepted.
These actions update release governance metadata. Deployment, runtime verification and human acceptance remain separate.
Requires the existing scoped rollback authorization or an approved return-to-Stable operation. No global Stable pointer is changed by this view.
Inspect or submit a policy draft for business review. Submitting a draft does not authorize deletion.
Inspect the authoritative current writer. Initialization requires the existing verified ownership and admission controls.
Manage platform security controls and review security-sensitive administration settings.