

INTERNAL PLATFORM · ENTRA ID REQUIRED
A private, internal enterprise AI platform for our Microsoft 365 organisation — for everyday employees, department administrators and platform administrators. It brings ChatGPT-style assistance, document analysis, departmental workspaces and cost visibility together behind one boundary. Entra ID sign-in is required.
Corporate identity establishes every employee before any request is accepted.
Role-based membership scopes content to the department it belongs to.
FINLEGENGRequests are routed through the platform to OpenAI’s API, with model and version recorded.
Retention policy applied at the provider boundary, where approved and available.
ZDR · subject to provider approval01Platform
Private, ChatGPT-style conversationA private conversation workspace for internal employees, with durable conversation history so earlier exchanges can be reopened and continued.
Secure document upload and analysisDocuments are uploaded into the platform for analysis, summarization and drafting grounded in the uploaded material.
Multiple versioned modelsA model selection is held with each conversation, and the platform is built to adopt newer models as they become available.
A private, internal enterprise AI platform for Microsoft 365 organisations. It serves internal employees, department administrators and platform administrators — and every protected surface requires Entra ID sign-in.
Access begins with your corporate Microsoft Entra ID account. The platform does not keep its own passwords or account-creation flow; the identity provider establishes who you are each time you sign in.
Each departmental workspace is a separate boundary. Membership decides which workspaces you can enter; your assigned role decides what you can do inside one. Workspace owners manage their department’s membership and roles.
Zero Data Retention (ZDR) is part of the platform’s design, subject to OpenAI provider approval and technical availability. Where those conditions are not met, the platform states the actual retention state rather than claiming ZDR.
Retention policies are configurable by administrators, so the stated state reflects the deployment you are actually using.
03 Departments
Each department works in its own workspace, with access governed by role-based controls. Every workspace carries the same colour line segment and code wherever it appears.
A separate Finance workspace holds that department’s conversations and documents, scoped so only assigned Finance members reach them.
Role-based
Legal keeps its own workspace and membership, with access granted through assigned roles rather than shared credentials.
Role-based
Engineering works inside its departmental workspace, in line with the same access rules applied across every department.
Role-based
04Cost
Cost visibility breaks usage down by department, user and project, so the organisation can see where its private AI capacity is being consumed and plan against it. The panel below shows the ruled label/value format the AI spending dashboard uses.
Cost visibility is a platform administrator capability. Spending views are available to platform administrators, not to every employee.
No comments yet. Be the first!