[Control Center] Company Guidelines

content/en/docs/control-center/company/_index.md

@@ -2,7 +2,7 @@
 title: "Company"
 url: /control-center/company/
 description: "Describes the Company category in the Mendix Control Center."
-weight: 60
+weight: 70
 no_list: false
 ---
 ## Introduction 

content/en/docs/control-center/content-curation/_index.md

@@ -2,7 +2,7 @@
 title: "Content Curation"
 url: /control-center/content-curation/
 description: "Describes the Content Curation category in the Mendix Control Center."
-weight: 80
+weight: 90
 no_list: false
 ---
 ## Introduction 

content/en/docs/control-center/entitlements/_index.md

@@ -2,7 +2,7 @@
 title: "Entitlements"
 url: /control-center/entitlements/
 description: "Describes the Entitlements category in the Mendix Control Center."
-weight: 30
+weight: 40
 no_list: false 
 ---
 

content/en/docs/control-center/maia/_index.md

@@ -0,0 +1,13 @@
+---
+title: "Maia"
+url: /control-center/maia/
+description: "Describes the Maia category in the Mendix Control Center."
+weight: 30
+no_list: false 
+---
+
+## Introduction
+
+The **Maia** section allows you to manage, control, and monitor Maia behavior on Mendix Portal.
+
+## Documents in This Category

content/en/docs/control-center/maia/company-guidelines.md

@@ -0,0 +1,84 @@
+---
+title: "Company Guidelines"
+url: /control-center/company-guidelines/
+description: "Describes the Company Guidelines page in the Mendix Control Center."
+weight: 10
+beta: true
+---
+
+{{% alert color="warning" %}}
+This feature is in Public Beta. For more information, refer to [Release Status](/releasenotes/release-status/).
+{{% /alert %}}
+
+## Introduction
+
+Without centralized guidelines, developers must manually apply your organization's architectural patterns, compliance policies, and naming conventions to every Mendix project. The **Company Guidelines** page solves this by teaching Maia your company's standards. You define guidelines in a central location, and Maia automatically applies them across all projects. This ensures consistent, compliant outputs, which are aligned with your organization's standards.
+
+Company guidelines define the following:
+
+* Guidelines and standards – Compliance, security, and governance policies that teams must follow.
+* Reusable assets and conventions – Architecture and integration standards, development and design best practices.
+* Shared terminology – Domain language and company-specific terminology.
+
+When you upload company guideline documents, the system extracts and categorizes guidelines, which you can then review and approve. Once approved, these guidelines are stored in a central library, and are automatically served to Maia services. This ensures consistent AI generation across your software delivery lifecycle.
+
+## Managing Company Guidelines
+
+To upload, review, and create company guidelines, follow these steps:
+
+1. Click **Upload Document**. You can upload .md, .pdf, .docx, .xlsx, and .txt format documents. For an example of what constitutes a good guideline document, check out <a href="/originals/control-center/company-guidelines/Evora Development Guidelines.pdf" target="_blank" rel="noopener noreferrer">this sample .pdf</a>.
+
+2. Once you are done uploading, click **Process Documents**. The newly uploaded documents are displayed in the **Documents that need your attention** section, pending processing and review.
+
+    Mendix parses and processes the uploaded documents in the background. During this time, the status of the documents is **Processing**. After processing is complete, the status changes to **Pending Review**, and a **Review Guidelines** button is displayed on the document card.
+
+3. Click **Review Guidelines** to go through the pre-processed list of guidelines and approve them. The **Review Proposed Guidelines** page is displayed, showing a list of all the guidelines in the document, along with the categories they fall under. These categories are generated and assigned by Mendix AI agents. For details on the available categories, refer to the [Guideline Categories](#guideline-categories) section of this page.
+
+    You can perform the following actions for each guideline in the list:
+
+    * Click **Mark as Reviewed** if you want to keep the guideline and its assigned categories.
+    * In the contextual menu, click **Edit** if you want to edit a guideline and its categories.
+    * In the contextual menu, click **Remove** if you want to discard the guideline.
+
+    You can search by guideline text, or filter by category and status.
+
+4. After you have reviewed all the guidelines in the list, click **Create Guidelines**. The guidelines are now listed on the **Company Guidelines** tab of the main page.
+
+### Guideline Categories {#guideline-categories}
+
+After a document is parsed, guidelines are automatically assigned to one or more categories. These are the possible categories:
+
+* Domain terminology – Guidelines in this category define what a term, concept, severity level, tier, or process state means, so agents interpret it consistently.
+* Architecture and integration – Guidelines in this category govern how services communicate, integrate, or expose contracts to other systems: API contracts, protocols, payload formats, versioning, service topology, cross-system schemas.
+* Data and domain modeling – Guidelines in this category govern how data is structured, named, typed, owned, classified, or modeled within or across services: entity design, field names, schema ownership, domain boundaries.
+* Development standards – Guidelines in this category govern how code is written, tested, reviewed, named, built, deployed, or operated inside a single service or team: coding conventions, branch naming, internal tooling.
+* Security – Guidelines in this category impose a technical control: encryption, authentication, authorization, secrets management, input validation, vulnerability management, access controls.
+* Compliance and governance – Guidelines in this category impose a regulatory obligation, audit/evidence requirement, approval workflow, or governance process with an accountability trail: mandated processes, sign-offs, deadlines with owners.
+* Design and brand – Guidelines in this category govern visual design, UX behaviour, copywriting, tone, or brand identity on user-facing surfaces: layouts, colors, typography, voice, accessibility.
+
+## Company Guidelines Page Tabs
+
+The main **Company Guidelines** page includes the **Company Guidelines** and **Source Documents** tabs.
+
+### Company Guidelines Tab 
+
+The **Company Guidelines** tab lists all the guidelines that have been processed and approved, along with their categories. Each guideline has the following details:
+
+* The approver
+* The source document
+* A contextual menu which includes the options to edit or delete the guideline
+
+You can search by guideline text, or filter by category and source file.
+
+### Source Documents Tab 
+
+The **Source Documents** tab lists the documents from which approved guidelines originate, along with the following details:
+
+* **Document name** – The name of the uploaded document.
+* **Uploaded by** – The name of the user who uploaded the document.
+* **Date** – The date when the document was uploaded.
+* **Status** – The status of the document, which can be one of the following:
+    * **Processing**
+    * **Pending Review** – Click **Review** to go through the list of guidelines.
+    * **Applied**
+* **Delete** – Delete the document. This deletes all of its associated guidelines.

content/en/docs/control-center/marketplace/_index.md

@@ -2,7 +2,7 @@
 title: "Marketplace"
 url: /control-center/marketplace/
 description: "Describes the Marketplace category in the Mendix Control Center."
-weight: 70
+weight: 80
 no_list: false
 ---
 ## Introduction 

content/en/docs/control-center/people/_index.md

@@ -2,7 +2,7 @@
 title: "People"
 url: /control-center/people/
 description: "Describes the People category in the Mendix Control Center."
-weight: 50
+weight: 60
 no_list: false
 ---
 

content/en/docs/control-center/security/_index.md

@@ -2,7 +2,7 @@
 title: "Security"
 url: /control-center/security/
 description: "Describes the Security category in the Mendix Control Center."
-weight: 30
+weight: 50
 no_list: false
 ---
 

content/en/docs/releasenotes/control-center/2026.md

@@ -7,6 +7,15 @@ weight: 1
 numberless_headings: true
 ---
 
+## July 2026
+
+### July 1, 2026
+
+#### New Features
+
+* You can now use the new **Company Guidelines** page to define and manage organization-wide development standards that enable Maia to generate outputs aligned with your requirements. From there, you can upload company guideline documents, which are then stored in a central library and automatically served to Maia services. This ensures consistent AI generation across all projects, and eliminates the need to manually reapply standards for each development effort.    
+    For details, refer to [Company Guidelines](/control-center/company-guidelines/).
+
 ## June 2026
 
 ### June 17, 2026