Enterprise administration

    OneAdmin

    Administration with clear authority.

    Request a walkthroughProduct site (opens in a new tab)
    OneAdmin · Control-model illustration · no live execution
    Who buys it
    BI and EPM administrators, IT operations, and governance leaders
    The job it addresses
    Inspect enterprise administration context and route agent proposals to the administrator who is accountable for the decision.
    What you end up with
    A proposal a named administrator can inspect, approve, reject, or hold — with the action recorded.
    Where it stops
    Inspection and request preparation are implemented against admitted assets and uploaded snapshots. The approval and execution interaction on this site and on the product site is a simulated preview; unified execution across systems is planned, not shipped.

    Next step

    OneAdmin brings enterprise administration into context, with a product direction centred on agent proposals, administrator authority, and traceable actions. Platform inspection and request preparation are separate from the approval and execution preview.

    Request a walkthroughGo to the OneAdmin site(opens in a new tab)

    Plans and pricing live on the product site, where they stay current.

    The workflow, end to end

    Input, action, artifact, human review, outcome — and an honest account of how far the evidence currently goes.

    An administrative proposal reaching the accountable administrator

    Synthetic browser state — no backend enforcement · inspected 2026-09-26

    Interactive preview — simulated execution
    Interactive product preview — simulated execution
    1. 1

      Input

      An agent proposal describing an exact administrative change.

    2. 2

      Action

      The proposal is routed to the administrator who holds the authority for it.

    3. 3

      Artifact

      The proposal, the authority that applies, and the policy that governs it.

    4. 4

      Human review

      The administrator approves, rejects, holds, or is denied by policy.

    5. 5

      Outcome

      A receipt recording who decided what, and when.

    What this supports

    • The authority model is coherent and inspectable: proposal, authority, policy, decision, receipt.
    • Unauthorised attempts and policy denials are modelled explicitly, not as an afterthought.

    What this does not support

    • That the approval or execution shown runs against a live system.
    • That OneAdmin enforces policy across connected systems today.

    Recording still owed

    A separate recording of a supported snapshot inspection or request preparation flow. It must never be edited together with the authority preview into one video that implies a complete live execution chain.

    What it does today

    Status is per operation and per platform, because that is the level at which it actually varies. A route existing in the product is not the same as a product owner releasing it.

    OneAdmin capabilities by operation, platform scope, status and limitations
    OperationPlatform scopeStatusLimitations
    Inspect Power BI models, workspaces, and measure-to-column dependenciesPower BI assets admitted to the configured scopeSource-backedreviewed 2026-09-26
    • Scoped to admitted assets. Discovery of every asset in a tenant is not implied.
    Parse an uploaded Oracle EPBCS application snapshot and inspect its artifactsOracle EPBCS application snapshotsSource-backedreviewed 2026-09-26
    • A snapshot is not live Oracle state. Findings describe the uploaded artifact at its export time.
    Prepare an administrative request with tenant scope and delegation checksDocumented intake and preparation flowSource-backedreviewed 2026-09-26
    • Preparation is not execution. Automatic agent invocation remains incomplete in the documented evidence.
    Inspect a proposal and exercise approval, rejection, hold, and policy denialWebsite and product-site demonstrationInteractive preview — simulated executionreviewed 2026-09-26
    • Synthetic browser state. It demonstrates the intended interaction and authority model, not backend enforcement.
    • Receipts shown in the preview are simulated.
    Approve once and execute across connected systemsCross-system dispatchPlannedreviewed 2026-09-26
    • The coverage matrix marks unified execution planned, and reviewed documentation reports unified dispatch returning HTTP 501.
    • Universal approve-and-execute and universal policy enforcement are not offered.
    Trace dependencies across connected systemsCross-system lineagePlannedreviewed 2026-09-26
    • Marked planned in the product coverage data. A lineage illustration is not proof of a live cross-system dependency graph.
    Publish to Power BI through the dedicated publishing workflowPower BISource-backedreviewed 2026-09-26
    • A dedicated publishing path for one platform is not evidence of a universal OneAdmin execution gate.

    How to read the status labels

    Source-backed
    The implementation exists in the inspected product source. It has not been demonstrated end to end here.
    Demonstrated
    A dated end-to-end run supports this capability, with environment, inputs and outputs recorded.
    Available
    A product owner has approved this capability for a stated customer scope and operating model.
    Interactive preview — simulated execution
    An illustrative interface or synthetic simulation. No live backend behaviour is implied.
    Planned
    Roadmap work. A component, route or partial API may already exist; the capability does not.

    The other two products

    Bahulam

    Connected intelligence for real work.

    Bring conversations, coding, tools, and domain workspaces around the task a team needs to complete.

    Bahulam in detail

    CoDash

    Modernise your BI estate.

    Understand what exists across the BI estate, decide what matters, migrate selected assets, and build and validate reporting.

    CoDash in detail