{"resourceId":"stanford-fin-oracle-authority-agent-20260803","versions":[{"version":"external-a01afccbc88eff0da41d5194d7de5f4475ff07ebc722a13fc863222957c61bb9","resource":{"id":"stanford-fin-oracle-authority-agent-20260803","title":"Stanford FIN finance agent mirrors Oracle authority and adds expense/PCard lookups","organization":"Stanford University Financial Management Services","sector":"Higher education / finance and administrative systems","geography":"United States (California)","publishedAt":"August 3, 2026","publicationDate":"2026-08-03","eventDate":null,"sourceName":"Stanford Fingate","sourceLabel":"Stanford FMS FIN pilot update","sourceUrl":"https://fingate.stanford.edu/newsroom/financial-info-navigator-fin-pilot","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["knowledge-work","data-security","governance-procurement","operating-model"],"finding":"Stanford FMS documents FIN, an AI Playground agent grounded in Fingate, Administrative Guide, and read-only Oracle Financials modules. Access to expense, PCard, PO, and approver data is gated by existing Oracle authority privileges; unauthorized asks receive an explicit permissions denial. August 2026 enhancements added expense/PCard lookups. FMS states FIN is not for content generation or task completion and that users must verify critical details.","sledRelevance":"Campus finance operations pattern: retrieve transactional status through an assistant while preserving ERP entitlement boundaries rather than granting the model broader finance visibility.","evidence":"Official FMS product page with capability table mapping views to SU authority privileges, sample prompts, launch notes (Feb and Aug 2026), and explicit limitations. No measured ticket diversion, time savings, or error rates.","architectureImplications":"Interpretation: bind the agent to read-only ERP queries and reuse Authority Manager entitlements; publish source refresh cycles; keep write/action paths out of scope. SSO to AI Playground is the front door.","governanceImplications":"Interpretation: policy/procedure grounding plus human verification language reduces but does not eliminate hallucination risk for finance guidance. Document which modules are in-bounds.","securityPrivacyImplications":"Permission mirroring is the primary control: FIN refuses detail the user cannot see in Oracle. Still requires monitoring of prompt logs and least-privilege authority assignments.","caveats":"No quantitative service outcomes; effective date of capabilities depends on user authority; responses may be incomplete; page is operator documentation, not an evaluation.","streamIds":["campus-operations"],"roles":{"sales":"Finance and controller shops want faster status lookups without opening ERP access wider than today. Stanford FIN is an entitlement-preserving chat agent over Fingate, the Administrative Guide, and read-only Oracle modules for expenses, PCard, POs, suppliers, and approvers. Unauthorized asks receive an explicit permissions denial. Sell a bounded read-only finance navigator pilot with privilege mapping and verification language, not autonomous AP or guaranteed ticket elimination. Ask how refresh cycles are disclosed and who owns Authority Manager parity before promising operational savings.","engineering":"Fit is an SSO-fronted agent over documented policy sites and named Oracle query modules, denying answers outside the user’s privileges. Bind the agent to read-only queries, publish source refresh metadata, keep write and posting paths out of scope, and log prompts. Prerequisites are an Authority Manager inventory, module allowlists, and regression tests that unauthorized users cannot see foreign transactions. Constraints: FIN is not designed to generate content or complete tasks, and users must still verify critical details in source systems. Security hinges on entitlement reuse, not model cleverness.","delivery":"Work includes privilege-to-question mapping tables, staged module enablement from approvers to expense and PCard lookups, prompt guidance, and a feedback-ticket loop. Ownership is Financial Management Services with IAM and ERP platform partners. Teach users to supply transaction IDs and date ranges and to treat answers as navigation, not posting authority. Acceptance criteria are a documented privilege matrix, a passing unauthorized-access test suite, and published limitation language. Risks include privilege misconfiguration, stale refresh cycles, and users treating chat output as approval."},"roleDetails":{"sales":{"customerProblem":"Faculty and staff spend time hunting policy pages and Oracle screens for routine finance status and how-to questions.","stakeholders":["Controller/FMS","Procurement","IAM/Authority Manager owners","Financial support center"],"discoveryQuestions":["Which Oracle modules and privileges map to each question type?","Will the agent be write-capable or read-only?","How are refresh cycles disclosed?","What verification expectation is communicated to users?"],"valueHypothesis":"An authority-aware finance navigator can speed status and policy lookup while keeping ERP entitlements intact; Stanford documents the pattern but not measured savings.","potentialEngagement":"90-day read-only pilot for PO/expense status and policy Q&A with privilege test cases and feedback loop.","unsupportedClaims":["Measured reduction in finance tickets","Safe write/automation of approvals","Error-free policy answers"]},"engineering":{"fit":"Read-only finance assistant grounded in policy sites and ERP query modules with entitlement checks.","architectureIntegration":"SSO into institutional AI Playground; connectors to Fingate, AGM, and named Oracle query modules; denial responses when privilege missing.","prerequisites":["Authority privilege inventory","Module allowlist","Refresh-cycle metadata","Prompt/logging controls"],"constraints":["Not designed to generate content or complete tasks","Detail visibility mirrors Oracle associations","User must verify critical details"],"security":"Reuse Oracle authority; refuse unauthorized detail; monitor prompts for sensitive PTA/payee fishing.","proofOfValue":["Automated tests that unauthorized users cannot see foreign transactions","Sampled answer grounding to linked sources","Support-center feedback themes"]},"delivery":{"work":"Map privileges to question classes, enable modules in stages, publish prompt guidance, and operate feedback tickets.","dependencies":["Oracle Financials","Authority Manager","AI Playground platform","Fingate/AGM content owners"],"ownership":"Financial Management Services with IAM and ERP platform partners.","skillsAdoption":"Users need prompt specificity with transaction IDs and date ranges; support staff coach verification habits.","governanceCheckpoints":["Module go-live review","Privilege regression tests","Periodic sampling of answers vs source systems"],"acceptanceCriteria":["Documented privilege matrix","Passing unauthorized-access test suite","User-facing limitation language published"],"risks":["Privilege misconfiguration leaking finance data","Users treating answers as posting authority","Stale refresh cycles"]}},"retrievedAt":"2026-09-15T18:49:20Z","enrichedAt":"2026-09-15T18:57:40Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"May reduce navigation burden for staff who can use chat interfaces; no accessibility evaluation of the Playground agent is provided. Does not address finance staff workload quantitatively.","procurementImplications":"Build-with-platform pattern (institutional AI Playground plus ERP) rather than a standalone finance bot; procurement should still cover logging, retention, and model hosting terms.","operatingModelImplications":"Central FMS owns the agent; users keep existing Oracle authorities; support center remains the escalation path for verification.","sourceVerification":{"openedUrl":"https://fingate.stanford.edu/newsroom/financial-info-navigator-fin-pilot","referenceExcerpt":"FIN restricts access to certain information based on your Oracle authority.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}