Know the User and Tenant
Establish the user, service identity, role, tenant and permitted operating scope.
MedhaOS
Keep AI Useful Without Giving Up Control
MedhaOS keeps identity, permissions, policies, approvals, audit and deployment boundaries around AI-enabled work so people remain in control of what the system may see, suggest and do.
Why control matters
Keep AI Authority Bounded
AI can interpret, investigate and propose useful work. That does not mean it should automatically gain access, approval rights or unrestricted execution power.
Who Is Acting Is Unclear
The system cannot reliably apply the right access and responsibility without knowing the user, tenant and role.
Authority Expands Quietly
Helpful reasoning can turn into unapproved action when permission and approval boundaries are not explicit.
The Decision Trail Disappears
Teams struggle to reconstruct which information, policy, approval or tool produced an outcome.
Sensitive Work Crosses Boundaries
Data, model endpoints and enterprise integrations can move beyond the intended operating boundary without clear controls.
MedhaOS value
Control Work Around AI
MedhaOS separates intelligence from authority so enterprise teams can define who may access, approve, execute and override AI-enabled work.
Know Who Is Acting
Connect users, groups, roles and service identities to the context, tools, routes and actions they are allowed to use.
Keep Customers Separate
Maintain customer, workspace, user and data boundaries according to the deployment and operating model.
Decide What AI May Do
Apply policies to what the system may see, retain, suggest, route, execute, escalate or block.
Require Approval Where It Matters
Keep consequential actions answerable to authorised people through explicit approval and escalation paths.
Keep a Reviewable History
Preserve requests, evidence, model or rule paths, policy checks, approvals, exceptions and outcomes.
See Usage and Cost
Provide operational visibility into routes, model usage, policy outcomes and cost-aware governance.
How control is applied
Identity to Accountable Action
Reasoning, permission, approval and execution remain separate responsibilities.
01 / 06Scroll to explore
Check the Policy
Apply data access, retention, model, route, tool and action constraints.
Allow the Right Reasoning
Let Medha retrieve and reason only within the approved context and capability boundary.
Ask for Approval
Escalate sensitive, irreversible or exceptional actions to an authorised person.
Execute and Record
Run only permitted tools and preserve the decision and execution history.
Stop or Correct
Keep operational override, interruption and correction paths available when they are needed.
Governance and security
Keep Important Controls Reachable
Security matters most when legitimate authority can still change what the system is allowed to do.
Least-Privilege Tool Access
Expose tools and APIs according to identity, tenant, route and task requirements rather than platform-wide convenience.
Privacy and Data Boundaries
Filter, de-identify, retain locally or rehydrate sensitive information inside controlled boundaries.
Private and Hybrid Deployment
Place control, data-handling and execution components according to customer infrastructure and policy requirements.
Adoption
Fit Controls to Operations
Governance controls should be configured and tested against the real identity, authority and operating boundaries of each implementation.
Verify the Controls
Test identity, tenant, policy, approval and audit controls against the implementation.
Keep Ownership Explicit
Business and technical owners remain accountable for consequential actions and operating changes.
Confirm the Environment
Validate identity providers, permissions, retention and deployment boundaries for the environment.
Continue exploring
Control Plane in Context
Continue into governance, deployment and a guided MedhaOS walkthrough.
Governance and Security
Review identity, tenant, policy, privacy, approval, audit and operational override principles.
Deployment
Compare cloud, private cloud, hybrid and customer-controlled deployment patterns.
MedhaOS Walkthrough
Follow identity, permitted tools, policy, approval, execution and audit evidence in one guided scenario.
Start with the authority question