The responsible admin approves.
- 01 / Review the exact change and target.
- 02 / Inspect impact, risk, and missing evidence.
- 03 / Approve or reject the specific proposal.
Pending or rejected? Execution stays blocked.
Enterprise administration / Human authorityAGENT INITIATED. ADMIN CONTROLLED.
Agents propose.
Your admins decide.
OneAdmin is built around an admin inbox and an explicit execution gate: human approval or a previously assigned policy. Agent-triggered work stays visible, from proposal to result.
Walk through the control modelONE REQUEST. EVERY DECISION.Follow the action.
Follow the action.
Find the authority.
Choose a proposal. Follow its gate.
Make the decision in the inbox below.
BI-104 The agent has proposed a change. Without approval or an applicable assigned policy, it stops here.
AgentHuman decisionPolicy authorityHeldVerifiedSYNTHETIC WORKFLOW · NO LIVE EXECUTION
BI-104 / AGENT-ORIGINATED REQUESTProduction
Update the Budget variance measure
Power BI workspace agentDecision owner: Anika Shah
Finance requested a percentage variance. The agent proposes the expression below for administrator review.
CURRENT / SAMPLE CONTEXT
SUM(Finance[Actual]) - SUM(Finance[Budget])
PROPOSED / NOT YET APPLIED
DIVIDE( SUM(Finance[Actual]) - SUM(Finance[Budget]), SUM(Finance[Budget]) )
Scope & impact evidence
- Measure: Finance[Budget variance]
- References: Finance[Actual], Finance[Budget]
- Downstream report impact: not verified
Execution held · waiting for your approval
The agent can submit this proposal. It cannot execute without your decision or an applicable assigned policy.
Demonstrates the hold. No approval or assigned policy means no execution.
Control-model preview. Synthetic data and simulated execution. The unified approval/execution gate and per-admin routing shown here are the intended product experience, not a claim of deployed end-to-end enforcement. Current scope
01The control model / Human in the loop
Two ways to authorize.
No unaccounted action.
The intended contract is the same for every initiator: agent, administrator, or integration. A trigger creates a request. It does not grant permission to execute.
TARGET CONTROL MODEL · UNIFIED ENFORCEMENT PLANNEDFirst: identity, delegation, and target scope
Approval and policy both operate within an authorized scope. Neither expands the actor’s underlying permissions.
OR
An explicit policy covers it.
- 01 / Assigned by an authorized admin before the request.
- 02 / Matches the agent, action, target, and risk.
- 03 / Active at execution time, within its limits.
Missing, expired, or out of scope? Back to the admin.
One retained record: request → authority → execution → verification
Policy-covered work remains in the admin’s view with the policy version and assignment. Human-approved work retains its reviewer. Blocked attempts and rejections remain visible too.
02Lineage / Evidence for the approval
See beyond the asset.
Follow the consequence.
A change starts in one place. Its consequences can travel through planning models, calculations, reports, and teams.
The approval should carry that evidence: what changes, what depends on it, and which impacts remain unverified.
FINANCE OPERATIONS / DEPENDENCY MAPPRODUCT VISION · SAMPLE DATA
VERIFY LINK
FEEDS*
SELECTED CONTEXT / Model context
Analytics operations
The admitted model provides the structure for inspecting calculations and supported column dependencies.
*The cross-system map is illustrative. Current Power BI dependency coverage starts at measure-to-column relationships; enterprise asset lineage is planned.
Explore the lineage roadmap03Integrations / Native depth, connected context
Your platforms.
A shared intelligence.
Platform-specific agents and tools are the design foundation. The intended shared gate brings each proposal into the responsible admin’s view, with its authority and recorded outcome.
01 / PLATFORM CONTEXT
BI
Power BI
Models, measures, workspaces
OR
Oracle EPBCS
Application snapshots & artifacts
INITIAL IMPLEMENTATION FOCUS
02 / SHARED ADMIN LAYERINBOX · AUTHORITY · RECEIPT
OneAdmin
Agent proposal.
Approval or assigned policy.
A retained decision record.
03 / YOUR OPERATING PROCESS
IN
Request intake
Manual requests & generic webhooks
WS
Admin inbox
Review, authorize, and follow the outcome
ServiceNow, Jira, and Slack provider workflows are planned extensions.
PLATFORM ROADMAP
Tableau / Looker / SAP BPC
Future coverageExplore capability-by-capability coverage
| Capability | Power BI | Oracle EPBCS |
|---|---|---|
| Inventory & inspection | Admitted models and workspaces | Uploaded application snapshots |
| Dependency context | Measure-to-column dependencies | Parsed application artifacts |
| Change preparation | Selected manual request workflows | Snapshot-based investigation |
| Live platform actions | Dedicated publishing workflow | Planned |
| Cross-system lineage | Planned | Planned |
| Unified approve & execute | Planned | Planned |
Implementation scope varies by platform and access method. This is not a general availability commitment.