[{"data":1,"prerenderedAt":1525},["ShallowReactive",2],{"site-nav-content":3,"blog:\u002Fblog\u002Fnimbus-vs-microsoft-copilot":177,"blog-index-copy":577,"blog:\u002Fblog\u002Fnimbus-vs-microsoft-copilot:surround":598,"hiring-banner-content":1494,"site-cta-content":1506},{"header":4,"productNav":9,"nav":42,"footer":61,"askAI":132,"id":161,"title":162,"archived":163,"authors":164,"badge":164,"body":165,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":173,"relatedHeading":164,"seo":174,"series":164,"sitemap":163,"status":164,"stem":175,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":176},{"productLabel":5,"loginLabel":6,"contactLabel":7,"contactSalesLabel":8},"Product","Log in","Contact","Get started for free",[10,14,18,22,26,30,34,38],{"label":11,"to":12,"description":13},"Overview","\u002Foverview","Seven layers. One closed loop.",{"label":15,"to":16,"description":17},"Conflux","\u002Fproduct\u002Fconflux","Where your team, workstreams, and agents meet.",{"label":19,"to":20,"description":21},"Agent Teams","\u002Fproduct\u002Fagent-teams","Specialist teams - governed from day one.",{"label":23,"to":24,"description":25},"Lifecycle Graph","\u002Fproduct\u002Flifecycle-graph","Intelligence that compounds across every interaction.",{"label":27,"to":28,"description":29},"Company Wiki","\u002Fproduct\u002Fwiki","Playbooks and policies where expertise stays.",{"label":31,"to":32,"description":33},"Workstreams","\u002Fproduct\u002Fworkstreams","From brief to signed-off deliverable on one canvas.",{"label":35,"to":36,"description":37},"Perception Console","\u002Fproduct\u002Fperception","Ask your whole business in plain English.",{"label":39,"to":40,"description":41},"Governance","\u002Fproduct\u002Fgovernance","Frontier AI you can actually sign off on.",[43,46,49,52,55,58],{"label":44,"to":45},"Models","\u002Fmodels",{"label":47,"to":48},"Pricing","\u002Fpricing",{"label":50,"to":51},"Integrations","\u002Fintegrations",{"label":53,"to":54},"Security","\u002Fsecurity",{"label":56,"to":57},"Partners","\u002Fpartners",{"label":59,"to":60},"Insights","\u002Fblog",{"productHeading":5,"companyHeading":62,"resourcesHeading":63,"legalHeading":64,"docsLabel":65,"docsUrl":66,"statementLines":67,"copyright":70,"companyLinks":71,"resourcesLinks":86,"legalLinks":102,"socialLinks":109,"bottomLinks":119},"Company","Resources","Legal","Docs","https:\u002F\u002Fdocs.gonimbus.ai",[68,69],"Stop training someone else's model.","Control your AI.","© 2026 Nimbus Intelligence, Inc. All rights reserved.",[72,73,74,75,76,78,81,84],{"label":47,"to":48},{"label":50,"to":51},{"label":53,"to":54},{"label":59,"to":60},{"label":77,"to":57},"Partner Program",{"label":79,"to":80},"Careers","\u002Fcareers",{"label":82,"to":83},"System status","\u002Fstatus",{"label":7,"to":85},"\u002Fcontact",[87,90,93,96,99],{"label":88,"to":89},"Glossary","\u002Fglossary",{"label":91,"to":92},"Compare","\u002Fcompare",{"label":94,"to":95},"Evaluate","\u002Fevaluate",{"label":97,"to":98},"Problems","\u002Fproblems",{"label":100,"to":101},"Use cases","\u002Fuse-cases",[103,106],{"label":104,"to":105},"Terms of Service","\u002Fterms",{"label":107,"to":108},"Privacy Policy","\u002Fprivacy",[110,113,116],{"label":111,"href":112},"LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fcompany\u002Fgonimbusai\u002F",{"label":114,"href":115},"X","https:\u002F\u002Fx.com\u002Fgonimbusai",{"label":117,"href":118},"Instagram","https:\u002F\u002Fwww.instagram.com\u002Fgonimbus_ai\u002F",[120,122,124,127,128],{"label":121,"to":105},"Terms",{"label":123,"to":108},"Privacy",{"label":125,"to":126},"Compliance","\u002Fcompliance",{"label":82,"to":83},{"label":129,"to":130,"external":131},"LLMs.txt","\u002Fllms.txt",true,{"text":133,"prompt":134,"platforms":135},"Ask AI about Nimbus","I'm researching enterprise intelligence platforms and want to know how Nimbus combines perception, collaboration, and autonomous agents to drive strategic decision-making. Summarize the highlights from Nimbus's website: https:\u002F\u002Fgonimbus.ai",[136,141,146,151,156],{"name":137,"label":138,"icon":139,"hrefPrefix":140},"chatgpt","ChatGPT","simple-icons:openai","https:\u002F\u002Fchatgpt.com\u002F?prompt=",{"name":142,"label":143,"icon":144,"hrefPrefix":145},"perplexity","Perplexity","mdi:magnify","https:\u002F\u002Fwww.perplexity.ai\u002Fsearch\u002Fnew?q=",{"name":147,"label":148,"icon":149,"hrefPrefix":150},"grok","Grok","simple-icons:x","https:\u002F\u002Fx.com\u002Fi\u002Fgrok?text=",{"name":152,"label":153,"icon":154,"hrefPrefix":155},"claude","Claude","simple-icons:anthropic","https:\u002F\u002Fclaude.ai\u002Fnew?q=",{"name":157,"label":158,"icon":159,"hrefPrefix":160},"google-ai","Google AI","simple-icons:google","https:\u002F\u002Fwww.google.com\u002Fsearch?udm=50&aep=11&q=","content\u002Fshared\u002Fnav.md","Site navigation",false,null,{"type":166,"value":167,"toc":168},"minimark",[],{"title":169,"searchDepth":170,"depth":170,"links":171},"",2,[],"md","\u002Fshared\u002Fnav",{"title":162,"description":169},"shared\u002Fnav","Q7sDe7TuGEwhwUMamyeOxjvGlsUaF3Iay9VTW0KaE_U",{"id":178,"title":179,"archived":163,"authors":164,"badge":180,"body":186,"date":552,"definedTerm":164,"department":164,"description":553,"extension":172,"eyebrow":164,"faqHeader":554,"faqs":557,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":567,"relatedHeading":164,"seo":568,"series":569,"sitemap":131,"status":164,"stem":570,"subhead":164,"tags":571,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":576},"content\u002Fblog\u002Fnimbus-vs-microsoft-copilot.md","Nimbus vs Microsoft Copilot: Great Inside Office, or Work That Leaves Microsoft?",{"label":181,"10|authors":182},"Comparisons",[183],{"name":184,"to":185},"Nimbus Research","https:\u002F\u002Fgonimbus.ai",{"type":166,"value":187,"toc":533},[188,213,216,238,243,299,303,309,321,328,340,343,346,350,353,356,359,362,365,369,382,400,408,415,419,424,427,431,434,438,443,447,454,458,461,465,468,472,479,483,489,493,508,512],[189,190,191,192,200,201,207,208,212],"p",{},"“Copilot” is several products that get collapsed in procurement. ",[193,194,195],"strong",{},[196,197,199],"a",{"href":198},"https:\u002F\u002Fwww.microsoft.com\u002Fmicrosoft-365\u002Fcopilot","Microsoft 365 Copilot"," is the add-on that sits in Word, Excel, PowerPoint, Outlook, Teams, and the Copilot app. ",[193,202,203],{},[196,204,206],{"href":205},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fmicrosoft-copilot-studio\u002F","Copilot Studio"," is the low-code environment for multi-step agents beyond Microsoft. Nimbus is an ",[196,209,211],{"href":210},"\u002Fblog\u002Fwhat-is-an-agent-harness\u002F","agent harness"," for work that leaves Microsoft — Salesforce, NetSuite, and the rest of the stack where money actually moves.",[189,214,215],{},"Nobody else will be as good at “summarise this thread and the attached deck” inside Outlook. That recap is tenant productivity. Updating forty opportunities in Salesforce is company operations. If your programme starts with “every knowledge worker has a Copilot licence,” you are specifying Microsoft. If it starts with “RevOps will not allow unapproved Salesforce writes from an agent, and we need a record of those releases,” you are specifying Nimbus. You can keep both. Using Nimbus does not mean ripping Copilot out of Office.",[189,217,218,219,223,224,228,229,233,234,237],{},"Microsoft’s own ",[196,220,222],{"href":221},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fmicrosoft-365\u002Fcopilot\u002Fmicrosoft-365-copilot-architecture","architecture"," and ",[196,225,227],{"href":226},"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fcopilot\u002Fmicrosoft-365\u002Fmicrosoft-365-copilot-privacy","privacy"," docs are the source: Copilot is grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access — and prompts, responses, and Graph data are not used to train foundation LLMs. That is the right privacy story for find-and-draft inside Microsoft. It still describes ",[230,231,232],"em",{},"find and draft inside Microsoft",", not ",[230,235,236],{},"sign a write in Salesforce",". Agent Builder covers simple agents inside Copilot, grounded in Microsoft 365 content, for information workers. Studio is the step that leaves Graph.",[239,240,242],"h2",{"id":241},"words-youll-hear","Words you’ll hear",[244,245,246,253,259,265,271,277,287,293],"ul",{},[247,248,249,252],"li",{},[193,250,251],{},"Microsoft 365 Copilot."," The per-person assistant inside Office, grounded in Microsoft Graph — mail, files, meetings, and sites the user can already access.",[247,254,255,258],{},[193,256,257],{},"Microsoft Graph."," The map of what this person can already open in Microsoft 365. Copilot should not leak a file they cannot open in SharePoint.",[247,260,261,264],{},[193,262,263],{},"Copilot Studio."," Low-code agents with branching, approvals, and connectors to Salesforce, SAP, ServiceNow, and custom APIs. You can publish to Teams. Metering is often credits or messages on top of licences.",[247,266,267,270],{},[193,268,269],{},"Agent Builder."," Simple agents inside Copilot, grounded in Microsoft 365 content, for information workers.",[247,272,273,276],{},[193,274,275],{},"Workstream."," In Nimbus, a shared workspace for one job across systems that are not all Microsoft.",[247,278,279,282,283,286],{},[193,280,281],{},"Write-back."," Changing a live system. You ",[230,284,285],{},"can"," update Salesforce from Studio. The update is a flow-shaped side effect in Microsoft’s world. In Nimbus it is a quoted release with a named signer.",[247,288,289,292],{},[193,290,291],{},"Lifecycle Graph."," The causal record of who approved, what changed, and what the next team should believe.",[247,294,295,298],{},[193,296,297],{},"E5."," Microsoft 365 E5 explains identity, compliance, and Office. It does not explain CRM write-back or a company work ledger.",[239,300,302],{"id":301},"why-the-difference-matters","Why the difference matters",[189,304,305,306,308],{},"Studio agents that leave Graph for other connectors inherit a different permission story: connector logins, rules that stop sensitive files leaking, environment strategy. IT knows this is where Copilot programmes stall. You ",[230,307,285],{}," update Salesforce from Studio. The update is a flow-shaped side effect in Microsoft’s world. In Nimbus it is a quoted release with a named signer. Approvals in a Power Platform artefact are real. They are not a Lifecycle Graph of the job across departments.",[189,310,311,312,316,317,320],{},"In Nimbus, the scarce resource is control of work across systems that are not all Microsoft. The quarterly review deck may live in SharePoint. The opportunities live in Salesforce. The revenue number finance trusts may live in NetSuite. A ",[196,313,315],{"href":314},"\u002Fblog\u002Fwhat-is-an-ai-workstream\u002F","workstream"," puts those in one job. Records stay read-only until someone who is allowed to approve writes actually does. The ",[196,318,23],{"href":319},"\u002Fblog\u002Fwhat-is-a-lifecycle-graph\u002F"," keeps the release.",[189,322,323,327],{},[196,324,326],{"href":325},"\u002Fblog\u002Fnimbus-vs-glean\u002F","Glean","-class search and Copilot-class Graph grounding solve findability. Nimbus assumes you can already find the policy. The failure is that AI work does not land in a signed-off artefact. Purpose limitation is easier to explain when a recruiting workstream cannot see finance forecasts. A Copilot licence that sees “whatever this user can already open” is a different design — Microsoft’s Graph design, by intention. That design is correct inside Office. It is a wide blast radius if the same licence is treated as the operating model for every system the user can already open.",[189,329,330,331,335,336,339],{},"Lock-in is the honest trade. Copilot deepens Microsoft 365. Nimbus is lock-in of a different kind: the work loop and the graph. If most proprietary work is already in Microsoft, Copilot’s return is easier. If most money-moving systems are Salesforce, NetSuite, and specialist software, Copilot Studio becomes a connector project — and Nimbus was designed as that project plus the record. E5 explains identity, compliance, and Office. It does not explain CRM ",[196,332,334],{"href":333},"\u002Fblog\u002Fwhat-is-write-back-governance\u002F","write-back",", choosing models across vendors, or a Lifecycle Graph. Standardise Copilot where Microsoft’s graph ",[230,337,338],{},"is"," the work. Standardise an operating layer where the business process is the work.",[189,341,342],{},"Role by role: a knowledge worker in Word, Excel, Outlook, and Teams wants the side pane — nobody else will recap the thread and the attached deck as well. IT owns Graph, licences, and often Studio as a Power Platform artefact: a helpdesk bot, an HR FAQ, a Teams helper. RevOps lives in Salesforce, not in SharePoint; a Studio connector to Salesforce is a flow-shaped side effect, not a company release. Finance trusts NetSuite, not the recap. Security will like Graph grounding and the privacy docs, and still ask who signed a CRM write. A CIO who already bought E5 should use Copilot where Microsoft’s graph is the work — and still not pretend E5 bought an operating layer.",[189,344,345],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model. Keep Copilot in Office. Put the job that leaves Microsoft in a workstream.",[239,347,349],{"id":348},"when-microsoft-copilot-is-a-better-fit","When Microsoft Copilot is a better fit",[189,351,352],{},"Choose Microsoft 365 Copilot when the job is knowledge-worker productivity in Word, Excel, Outlook, and Teams, and Microsoft’s own files and mail are the corpus.",[189,354,355],{},"Choose Copilot Studio when the agent is a Power Platform artefact IT will own — a helpdesk bot, an HR FAQ, a Teams helper. Metering is often credits or messages on top of licences; budget that as a Microsoft programme, not as a Nimbus substitute.",[189,357,358],{},"SharePoint agents are Q&A on sites. Use them for findability. Do not use them as the operating model.",[189,360,361],{},"Do not choose Copilot as a stealth operating layer for non-Microsoft systems. You will spend a year on connector reviews and still lack workstreams, specialist teams, and a Lifecycle Graph.",[189,363,364],{},"Keep Copilot in Office. Using Nimbus does not mean ripping it out. A coherent coexistence: Copilot for tenant productivity; Nimbus for jobs that also touch Salesforce, NetSuite, and the rest of the stack. Drafts can move from a recap into a workstream. Write credentials for money-moving systems should sit in Nimbus connector scopes, not in a Studio flow by default.",[239,366,368],{"id":367},"how-this-shows-up-in-nimbus","How this shows up in Nimbus",[189,370,371,372,376,377,381],{},"Nimbus does not try to be the Word side pane. It does not assume the only intelligence in the company is whatever Microsoft licensed this quarter. See ",[196,373,375],{"href":374},"\u002Fmodels\u002F","models",". Routing includes not throwing the most powerful model at a simple lookup. Treat Microsoft-hosted models as infrastructure options in an enterprise conversation with ",[196,378,380],{"href":379},"\u002Fcontact\u002F","sales",", not as a reason Copilot and Nimbus are the same product.",[189,383,384,385,389,390,394,395,399],{},"The ",[196,386,388],{"href":387},"\u002Fproduct\u002Fwiki\u002F","wiki"," is what the company asserts. ",[196,391,393],{"href":392},"\u002Fintegrations\u002F","Connectors"," are scoped per workspace. Agents get the systems you attached, in the mode you allowed, until a human releases a write. ",[196,396,398],{"href":397},"\u002Fproduct\u002Fagent-teams\u002F","Agent teams"," finish the work Copilot handed you after the recap.",[189,401,402,403,407],{},"You can ",[196,404,406],{"href":405},"\u002Foverview\u002F","set Nimbus up yourselves",". Copilot programmes at organisational scale are famous for implementation. Keep Copilot in Office; do not staff a consulting partner to invent an operating layer.",[189,409,410,411,414],{},"See ",[196,412,39],{"href":413},"\u002Fproduct\u002Fgovernance\u002F",".",[239,416,418],{"id":417},"questions-people-actually-ask","Questions people actually ask",[420,421,423],"h3",{"id":422},"does-nimbus-replace-microsoft-365-copilot","Does Nimbus replace Microsoft 365 Copilot?",[189,425,426],{},"No. Keep Copilot in Office. Nimbus does not try to be the Word side pane. It tries to be the place agent teams finish work that leaves Microsoft.",[420,428,430],{"id":429},"does-copilot-studio-replace-nimbus","Does Copilot Studio replace Nimbus?",[189,432,433],{},"Only if “a few Power Platform agents” is the entire AI programme. Studio can be shared inside the Microsoft tenant. It does not replace Nimbus as a governed execution layer with a company wiki and an operational ledger.",[420,435,437],{"id":436},"can-nimbus-use-azure-openai-or-microsoft-models","Can Nimbus use Azure OpenAI or Microsoft models?",[189,439,440,441,381],{},"Nimbus routes models for quality, cost, and latency — including not throwing the most powerful model at a simple lookup. Treat Microsoft-hosted models as infrastructure options in an enterprise conversation with ",[196,442,380],{"href":379},[420,444,446],{"id":445},"why-not-standardise-on-copilot-because-we-already-buy-microsoft-365-e5","Why not standardise on Copilot because we already buy Microsoft 365 E5?",[189,448,449,450,335,452,339],{},"E5 explains identity, compliance, and Office. It does not explain CRM ",[196,451,334],{"href":333},[230,453,338],{},[420,455,457],{"id":456},"do-we-need-a-microsoft-partner-to-get-nimbus-running","Do we need a Microsoft partner to get Nimbus running?",[189,459,460],{},"No. You can set it up yourselves. Copilot Studio at organisational scale usually is not self-serve in the same way.",[420,462,464],{"id":463},"can-we-keep-copilot-and-put-salesforce-writes-in-nimbus","Can we keep Copilot and put Salesforce writes in Nimbus?",[189,466,467],{},"Yes. That is the intended coexistence. Recap in Outlook; finish in a workstream. Do not let a Studio Salesforce connector become the unofficial write path “because we already had an approval step in the flow.” Quote the change, name the signer, store the outcome.",[420,469,471],{"id":470},"who-should-own-which-product","Who should own which product?",[189,473,474,475,478],{},"IT typically owns Microsoft 365 Copilot and Studio: licences, Graph, Power Platform environments. Line operators own Nimbus workstreams that touch Salesforce, NetSuite, and specialist systems. Security reviews Graph grounding ",[230,476,477],{},"and"," write gates. A single “we already pay Microsoft” owner will stretch Copilot into an operating layer.",[420,480,482],{"id":481},"what-about-glean-if-we-already-have-copilot","What about Glean if we already have Copilot?",[189,484,485,486,414],{},"Copilot respects Microsoft permissions inside Microsoft. Glean searches across many apps, including Microsoft, and respects source permissions. You may still need Glean if SharePoint search is not enough, and still need Nimbus if neither is an operating layer. See ",[196,487,488],{"href":325},"Nimbus vs Glean",[239,490,492],{"id":491},"related-reading","Related reading",[189,494,495,497,498,497,501,505,506,414],{},[196,496,211],{"href":210},", ",[196,499,500],{"href":333},"What is write-back governance",[196,502,504],{"href":503},"\u002Fblog\u002Fwhat-is-an-enterprise-ai-operating-system\u002F","What is an enterprise AI operating system",", and ",[196,507,488],{"href":325},[239,509,511],{"id":510},"sources","Sources",[244,513,514,518,523,528],{},[247,515,516],{},[196,517,199],{"href":198},[247,519,520],{},[196,521,522],{"href":226},"Microsoft 365 Copilot privacy",[247,524,525],{},[196,526,527],{"href":221},"Microsoft 365 Copilot architecture",[247,529,530],{},[196,531,532],{"href":205},"Microsoft Copilot Studio",{"title":169,"searchDepth":170,"depth":170,"links":534},[535,536,537,538,539,550,551],{"id":241,"depth":170,"text":242},{"id":301,"depth":170,"text":302},{"id":348,"depth":170,"text":349},{"id":367,"depth":170,"text":368},{"id":417,"depth":170,"text":418,"children":540},[541,543,544,545,546,547,548,549],{"id":422,"depth":542,"text":423},3,{"id":429,"depth":542,"text":430},{"id":436,"depth":542,"text":437},{"id":445,"depth":542,"text":446},{"id":456,"depth":542,"text":457},{"id":463,"depth":542,"text":464},{"id":470,"depth":542,"text":471},{"id":481,"depth":542,"text":482},{"id":491,"depth":170,"text":492},{"id":510,"depth":170,"text":511},"2026-08-17","Microsoft 365 Copilot lives in Word, Outlook, and Teams; Nimbus is for jobs that also touch Salesforce, NetSuite, and the rest of the business.",{"eyebrow":555,"title":556},"Short answers","Inside Office, or across the company",[558,561,564],{"question":559,"answer":560},"Where does Microsoft 365 Copilot live?","In Word, Outlook, and Teams. It is strong where the work already sits in Microsoft 365.",{"question":562,"answer":563},"When is that not enough?","When the job also touches Salesforce, NetSuite, or anything else outside that suite.",{"question":565,"answer":566},"Do we replace Copilot?","No. Keep it for Office work. Use Nimbus for the job that has to leave Microsoft and still have a signer.","\u002Fblog\u002Fnimbus-vs-microsoft-copilot",{"title":179,"description":553},"comparisons","blog\u002Fnimbus-vs-microsoft-copilot",[569,572,573,574,575],"microsoft-copilot","copilot-studio","m365","enterprise-ai","wOEE0tFNw3fpqNYUAVE31zDiChOKd5i0BdiFV9cFPyo",{"hero":578,"id":580,"title":581,"archived":163,"authors":164,"badge":164,"body":582,"date":164,"definedTerm":164,"department":164,"description":586,"extension":172,"eyebrow":587,"faqHeader":164,"faqs":164,"footerBand":588,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":60,"relatedHeading":594,"seo":595,"series":164,"sitemap":131,"status":164,"stem":596,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":597},{"filename":579},"u2221455217_Flat_design_of_a_futuristic_minimalist_landscape__5d589295-cdea-4ea9-a262-be766881accf_1.png","content\u002Fblog\u002Findex.md","Exploring the future of intelligence.",{"type":166,"value":583,"toc":584},[],{"title":169,"searchDepth":170,"depth":170,"links":585},[],"Deep dives into pre-cognitive intelligence, sentient enterprises, and the evolving landscape of AI-driven business transformation.","Latest Research",{"headline":589,"description":590,"primaryLabel":591,"primaryTo":592,"secondaryLabel":593,"secondaryTo":12},"Stay at the frontier.","Subscribe for product updates and new insights.","Subscribe","\u002Fnewsletter","Explore the platform","More research",{"title":581,"description":586},"blog\u002Findex","BFSWGYO9bcTlaulivKYWyg08_DJHsdGg3OC6g_CG1Hw",[599,1180],{"id":600,"title":601,"archived":163,"authors":602,"badge":604,"body":606,"date":552,"definedTerm":164,"department":164,"description":1158,"extension":172,"eyebrow":164,"faqHeader":1159,"faqs":1161,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1171,"relatedHeading":164,"seo":1172,"series":1173,"sitemap":131,"status":164,"stem":1174,"subhead":164,"tags":1175,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1179},"content\u002Fblog\u002Fwhat-is-ai-governance.md","What is AI Governance",[603],{"name":184,"to":185},{"label":605},"Explainer",{"type":166,"value":607,"toc":1134},[608,615,618,621,637,640,652,654,747,757,761,769,772,803,806,836,843,847,853,864,870,876,887,891,897,903,909,917,923,930,948,950,953,960,974,983,985,989,997,1001,1004,1008,1015,1019,1022,1026,1029,1033,1040,1044,1047,1051,1054,1058,1061,1065,1068,1072,1077,1081,1084,1086,1094,1096],[189,609,610,611,614],{},"AI governance is the set of rules, ",[193,612,613],{},"enforced in the software people actually use",", that decide who may use which AI, on which company data, and whether that AI is allowed to change a live business system — plus a record of what happened afterwards.",[189,616,617],{},"A training video is not that. An acceptable-use PDF is not that. An admin toggle the model can ignore is not that. If an unapproved change can still succeed, you have guidance, not governance.",[189,619,620],{},"People use the phrase for three different things, and they get mixed up:",[622,623,624,631,634],"ol",{},[247,625,626,627,414],{},"A public commitment — for example the ",[196,628,630],{"href":629},"https:\u002F\u002Foecd.ai\u002Fen\u002Fai-principles","OECD AI Principles",[247,632,633],{},"A company committee with a risk register.",[247,635,636],{},"The runtime that actually stops a change to CRM, ERP, or a customer message.",[189,638,639],{},"All three are real. Only the third one would have blocked an unlogged field change that later showed up in a forecast.",[189,641,642,646,647,651],{},[196,643,645],{"href":644},"https:\u002F\u002Fwww.gartner.com\u002Fen\u002Farticles\u002Fai-governance-trism","Gartner’s TRiSM"," language is about that third layer: trust, risk, and security around the systems that run — not a quarterly slide about principles. The ",[196,648,650],{"href":649},"https:\u002F\u002Fwww.nist.gov\u002Fitl\u002Fai-risk-management-framework","NIST AI Risk Management Framework"," says the same thing in public-sector language: Govern, Map, Measure, Manage. Mapping systems and measuring incidents still fail if the product people click can write to Salesforce without a named signer.",[239,653,242],{"id":241},[244,655,656,662,675,686,692,698,713,723,734],{},[247,657,658,661],{},[193,659,660],{},"Live business system."," CRM, ERP, HR, billing — the tools that hold official numbers and customer records. At work, this is where a fluent sentence becomes a fact other teams will inherit.",[247,663,664,667,668,671,672,674],{},[193,665,666],{},"Write \u002F write-back."," The AI is allowed to ",[230,669,670],{},"change"," that system, not only draft a suggestion. See ",[196,673,500],{"href":333},". At work, a next-step note and an Amount field are not the same risk class.",[247,676,677,680,681,685],{},[193,678,679],{},"Human-in-the-loop."," A person must approve before the job can finish. See ",[196,682,684],{"href":683},"\u002Fblog\u002Fwhat-is-human-in-the-loop-ai\u002F","What is human-in-the-loop AI",". At work, the gate shows the payload in the language of the live system, not a wall of prompt text.",[247,687,688,691],{},[193,689,690],{},"Named signer."," The identity that authorised the change. At work, “someone in the channel clicked yes” is not a signer.",[247,693,694,697],{},[193,695,696],{},"Fail-closed."," Missing approval means nothing happens. Fail-open means the change goes through unless someone happens to stop it.",[247,699,700,703,704,707,708,712],{},[193,701,702],{},"DPIA."," A data-protection impact assessment — thinking through purpose, risk, and personal data ",[230,705,706],{},"before"," you turn a tool loose. ",[196,709,711],{"href":710},"https:\u002F\u002Fico.org.uk\u002Ffor-organisations\u002Fuk-gdpr-guidance-and-resources\u002Fartificial-intelligence\u002F","UK ICO guidance on AI and data protection"," still wants a lawful basis and purpose when the “user” is an AI.",[247,714,715,718,719,414],{},[193,716,717],{},"Shadow AI."," Personal ChatGPT for work because the official path is missing. See ",[196,720,722],{"href":721},"\u002Fblog\u002Fwhat-is-shadow-ai\u002F","What is shadow AI",[247,724,725,728,729,733],{},[193,726,727],{},"Inventory."," A list of where AI actually runs. The ",[196,730,732],{"href":731},"https:\u002F\u002Fwww.justice.gov\u002Fmedia\u002F1373026\u002Fdl","US plan described in OMB M-24-10"," puts a named owner and an inventory first, not a PDF.",[247,735,736,739,740,743,744,746],{},[193,737,738],{},"Least privilege."," Only the data and tools required for ",[230,741,742],{},"this"," job. A ",[196,745,315],{"href":314}," is how that instinct becomes a company object.",[189,748,749,750,753,754,756],{},"Model safety is adjacent and different. Safety is about what a model will say in the abstract. Enterprise governance is about what ",[230,751,752],{},"your"," people and tools may do with ",[230,755,752],{}," systems and data. You can have a carefully aligned model and still have ungoverned CRM writes.",[239,758,760],{"id":759},"why-you-should-care","Why you should care",[189,762,763,764,768],{},"Without working rules, AI becomes a side effect. A field moves. A journal posts. A customer is told a policy the company does not hold. Nobody can say who allowed it. In February 2024, a British Columbia tribunal held Air Canada responsible for a chatbot that invented a bereavement-fare policy. ",[196,765,767],{"href":766},"https:\u002F\u002Fwww.cbc.ca\u002Fnews\u002Fcanada\u002Fbritish-columbia\u002Fair-canada-chatbot-lawsuit-1.7116416","CBC reported"," that the airline’s argument — the chatbot is a separate legal entity — failed. A customer-facing commitment without a working gate is still the company’s commitment.",[189,770,771],{},"It affects you if you:",[244,773,774,780,786,797],{},[247,775,776,779],{},[193,777,778],{},"Own a number."," Forecasts and close packs inherit whatever changed.",[247,781,782,785],{},[193,783,784],{},"Own a customer relationship."," Model output that becomes a commitment is still the company’s commitment.",[247,787,788,791,792,796],{},[193,789,790],{},"Own risk or legal."," Privacy law does not pause for a chatbot. ",[196,793,795],{"href":794},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2016\u002F679\u002Foj","GDPR"," still applies to purpose, minimisation, and erasure.",[247,798,799,802],{},[193,800,801],{},"Are asked “who is in charge of AI here?”"," An inventory and a named owner beat a principles slide.",[189,804,805],{},"Good governance in practice is four working rules:",[244,807,808,814,820,826],{},[247,809,810,813],{},[193,811,812],{},"People and rights."," Humans and AI tools are both actors. Roles decide what they may start, see, and sign.",[247,815,816,819],{},[193,817,818],{},"Data at question time."," Purpose and minimisation still apply when an AI is the one looking.",[247,821,822,825],{},[193,823,824],{},"Action rights."," Read-only is a control. Unrestricted tools are an incident waiting for a bad prompt.",[247,827,828,831,832,414],{},[193,829,830],{},"Evidence and spend."," Chat scrollback is not a management system. Uncapped spend is a budget failure and often a security failure. See ",[196,833,835],{"href":834},"\u002Fblog\u002Fwhat-is-ai-token-economics\u002F","What is AI token economics",[189,837,838,839,842],{},"Blocking consumer ChatGPT at the office network, while people use personal phones, is not governance. It is a ",[196,840,841],{"href":721},"shadow AI"," problem with extra steps.",[420,844,846],{"id":845},"what-changes-by-role","What changes by role",[189,848,849,852],{},[193,850,851],{},"Finance."," Governance is whether an AI-proposed journal can post, against which checklist, with which signer, and whether the spend of the run was capped. “Unlimited AI” is not a control. Surprise inference bills are a governance failure that looks like a cloud invoice.",[189,854,855,858,859,863],{},[193,856,857],{},"Legal."," Lawful basis, purpose limitation, customer-facing language, and reconstructable authorisation. Legal also has to separate the OECD-style public commitment from the runtime. A principles page does not implement Article-style oversight. For higher-risk systems, ",[196,860,862],{"href":861},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg\u002F2024\u002F1689\u002Foj","EU AI law"," Article 14 talks about effective oversight: people must be able to interpret outputs and interrupt the system. A footer that says “generated by AI” is not that.",[189,865,866,869],{},[193,867,868],{},"Operations."," Isolation of jobs, connector scope, and a place to put a paused run. Ops already runs change control. Governance is change control that includes a model as a proposer.",[189,871,872,875],{},[193,873,874],{},"Go-to-market."," The difference between a draft email and a sent commitment; between a suggested next step and a changed Amount. GTM feels friction first. The honest metric is time-to-approved-write, not time-to-first-answer.",[189,877,878,881,882,886],{},[193,879,880],{},"Security."," Identity of the connected user, read versus write, prompt injection as a path to a tool call, and the new store created by logs and indexes. The ",[196,883,885],{"href":884},"https:\u002F\u002Fgenai.owasp.org\u002Fllm-top-10\u002F","OWASP Top 10 for LLM applications"," treats retrieval and tool use as a security surface, not only a quality issue. Network DLP helps with paste-out. It does not quote a CRM change.",[420,888,890],{"id":889},"what-people-get-wrong","What people get wrong",[189,892,893,896],{},[193,894,895],{},"Governance as a committee."," Useful for risk registers. Useless if the product can still write.",[189,898,899,902],{},[193,900,901],{},"Governance as model safety."," Refusals on public-web questions do not bind Salesforce.",[189,904,905,908],{},[193,906,907],{},"Governance as a secure web gateway."," Necessary for some paste-out paths. Insufficient for writes, approvals, and causal history.",[189,910,911,914,915,414],{},[193,912,913],{},"Governance as blocking."," Blocks without a sanctioned path train people onto phones. See ",[196,916,722],{"href":721},[189,918,919,922],{},[193,920,921],{},"Theatre."," A checkbox, a prompt that says “ask first,” or an admin toggle the model can ignore.",[189,924,925,926,929],{},"Good looks like: connectors default to read-only; writes are quoted; a named signer cannot be waived by the model; evidence lives on a ",[196,927,928],{"href":319},"lifecycle graph","; spend has a ceiling; scope follows the job. Failure looks like a PDF, a blocked URL, and a personal API key in a wiki.",[189,931,932,933,936,937,940,941,943,944,947],{},"Adjacent concepts: ",[196,934,935],{"href":333},"write-back governance"," is the write subset. ",[196,938,939],{"href":683},"Human-in-the-loop"," is the gate. ",[196,942,31],{"href":314}," are the isolation unit. An ",[196,945,946],{"href":503},"enterprise AI operating system"," is the product shape that makes those rules the default path.",[239,949,368],{"id":367},[189,951,952],{},"Nimbus treats governance as how work is released, not as a sidecar policy engine.",[189,954,955,956,959],{},"Connectors — secure links to live systems — default to ",[193,957,958],{},"read-only",". When a change is proposed, the product shows the intended action and waits. A named person must sign. The model cannot waive the gate. Missing approval is fail-closed: nothing happens.",[189,961,962,963,965,966,968,969,973],{},"Scope is the ",[196,964,315],{"href":314},": one job, with the playbooks, systems, teams, and budget that belong to that job. Evidence is the ",[196,967,23],{"href":319},". The ",[196,970,972],{"href":971},"\u002Fblog\u002Fwhat-is-a-company-wiki-for-ai-agents\u002F","company wiki"," is the asserted policy the run must cite. Model routing does not bypass the gate.",[189,975,410,976,978,979,414],{},[196,977,39],{"href":413},". For scoring vendors: ",[196,980,982],{"href":981},"\u002Fblog\u002Fhow-to-evaluate-an-agent-harness\u002F","how to evaluate an agent harness",[239,984,418],{"id":417},[420,986,988],{"id":987},"is-ai-governance-the-same-as-making-the-model-safe","Is AI governance the same as making the model “safe”?",[189,990,991,992,753,994,996],{},"No. Model safety is about what the model will say in the abstract. Enterprise governance is about what ",[230,993,752],{},[230,995,752],{}," systems and data.",[420,998,1000],{"id":999},"can-we-rely-on-the-secure-web-gateway","Can we rely on the secure web gateway?",[189,1002,1003],{},"Network controls help with paste-out. They do not quote a CRM change, bind an approver, or store a causal history. Use both.",[420,1005,1007],{"id":1006},"must-a-person-always-approve","Must a person always approve?",[189,1009,1010,1011,1014],{},"For many operational writes, yes. For read-only analysis, maybe not. The mistake is calling a system “human-approved” because a human ",[230,1012,1013],{},"could"," look, while changes proceed on model initiative.",[420,1016,1018],{"id":1017},"do-the-oecd-ai-principles-require-a-specific-product","Do the OECD AI Principles require a specific product?",[189,1020,1021],{},"No. They are a public commitment. A product can make evidence cheaper to produce. The commitment does not implement a gate.",[420,1023,1025],{"id":1024},"is-a-dpia-enough-to-go-live","Is a DPIA enough to go live?",[189,1027,1028],{},"It is necessary thinking, not a runtime. You still need identity, scope, fail-closed writes, and a record. The DPIA should describe those controls, not replace them.",[420,1030,1032],{"id":1031},"does-blocking-chatgpt-count-as-governance","Does blocking ChatGPT count as governance?",[189,1034,1035,1036,1039],{},"It is a network control. Without a sanctioned path that can see the right files, people use personal phones. Blocking can tighten ",[230,1037,1038],{},"after"," substitution exists.",[420,1041,1043],{"id":1042},"how-is-this-different-from-it-change-management","How is this different from IT change management?",[189,1045,1046],{},"It is the same instinct — who may change production, with what evidence — applied to a proposer that speaks English. Existing CAB processes rarely see model-initiated payloads unless the product emits them.",[420,1048,1050],{"id":1049},"who-should-be-the-named-owner-of-ai","Who should be the named owner of AI?",[189,1052,1053],{},"Someone who can inventory systems and stop a write path, not a volunteer “champion” with no authority over CRM. Federal-style guidance starts with inventory and ownership for a reason.",[420,1055,1057],{"id":1056},"can-we-govern-only-customer-facing-chatbots-and-ignore-internal-copilots","Can we govern only customer-facing chatbots and ignore internal copilots?",[189,1059,1060],{},"Internal tools still process personal data and still write to live systems. Air Canada was customer-facing. Ungoverned CRM hygiene is an internal path to the same class of invented fact.",[420,1062,1064],{"id":1063},"do-we-need-the-eu-ai-act-if-we-are-not-a-high-risk-provider","Do we need the EU AI Act if we are not a high-risk provider?",[189,1066,1067],{},"You may still have GDPR duties, sector rules, and customer contracts. Oversight and records are useful even when a specific Act title does not apply. Do not claim “Act compliant” because you have a button.",[420,1069,1071],{"id":1070},"where-does-spend-fit","Where does spend fit?",[189,1073,1074,1075,414],{},"Uncapped inference is a control failure. Quotes, ceilings, and attribution by job are governance of a scarce, abusable resource. See ",[196,1076,835],{"href":834},[420,1078,1080],{"id":1079},"is-an-acceptable-use-policy-still-worth-writing","Is an acceptable-use policy still worth writing?",[189,1082,1083],{},"Yes, as communication. No, as enforcement. Write the PDF. Then put the same rules in the product people actually use.",[239,1085,492],{"id":491},[189,1087,1088,497,1090,505,1092,414],{},[196,1089,500],{"href":333},[196,1091,722],{"href":721},[196,1093,504],{"href":503},[239,1095,511],{"id":510},[244,1097,1098,1103,1107,1112,1116,1121,1125,1130],{},[247,1099,1100],{},[196,1101,1102],{"href":644},"Gartner, AI governance and TRiSM",[247,1104,1105],{},[196,1106,630],{"href":629},[247,1108,1109],{},[196,1110,1111],{"href":710},"ICO, AI and data protection",[247,1113,1114],{},[196,1115,650],{"href":649},[247,1117,1118],{},[196,1119,1120],{"href":766},"CBC, Air Canada chatbot lawsuit",[247,1122,1123],{},[196,1124,795],{"href":794},[247,1126,1127],{},[196,1128,1129],{"href":861},"EU AI Act (Regulation 2024\u002F1689)",[247,1131,1132],{},[196,1133,885],{"href":884},{"title":169,"searchDepth":170,"depth":170,"links":1135},[1136,1137,1141,1142,1156,1157],{"id":241,"depth":170,"text":242},{"id":759,"depth":170,"text":760,"children":1138},[1139,1140],{"id":845,"depth":542,"text":846},{"id":889,"depth":542,"text":890},{"id":367,"depth":170,"text":368},{"id":417,"depth":170,"text":418,"children":1143},[1144,1145,1146,1147,1148,1149,1150,1151,1152,1153,1154,1155],{"id":987,"depth":542,"text":988},{"id":999,"depth":542,"text":1000},{"id":1006,"depth":542,"text":1007},{"id":1017,"depth":542,"text":1018},{"id":1024,"depth":542,"text":1025},{"id":1031,"depth":542,"text":1032},{"id":1042,"depth":542,"text":1043},{"id":1049,"depth":542,"text":1050},{"id":1056,"depth":542,"text":1057},{"id":1063,"depth":542,"text":1064},{"id":1070,"depth":542,"text":1071},{"id":1079,"depth":542,"text":1080},{"id":491,"depth":170,"text":492},{"id":510,"depth":170,"text":511},"AI governance is the working rules for who may use which AI, on which data, and whether it may change a live business system.",{"eyebrow":555,"title":1160},"Rules that actually stop a change",[1162,1165,1168],{"question":1163,"answer":1164},"What is AI governance?","The working rules for who may use which AI, on which data, and whether it may change a live business system, plus a record of what happened.",{"question":1166,"answer":1167},"Is a policy PDF governance?","Only if the software enforces it. A document the model can ignore is guidance.",{"question":1169,"answer":1170},"What has to be true before a write?","A named person or a named rule has allowed that exact change. If they have not, the change does not happen.","\u002Fblog\u002Fwhat-is-ai-governance",{"title":601,"description":1158},"explainer","blog\u002Fwhat-is-ai-governance",[1173,1176,1177,1178],"governance","compliance","audit","3P7kWkstCX-Me3qq2PZcPS9sMhi7EacGegrGNsiBExQ",{"id":1181,"title":1182,"archived":163,"authors":164,"badge":1183,"body":1186,"date":552,"definedTerm":164,"department":164,"description":1472,"extension":172,"eyebrow":164,"faqHeader":1473,"faqs":1475,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1485,"relatedHeading":164,"seo":1486,"series":569,"sitemap":131,"status":164,"stem":1487,"subhead":164,"tags":1488,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1493},"content\u002Fblog\u002Fnimbus-vs-glean.md","Nimbus vs Glean: Finding the Deck vs Running the Job That Deck Implies",{"label":181,"10|authors":1184},[1185],{"name":184,"to":185},{"type":166,"value":1187,"toc":1454},[1188,1194,1201,1208,1210,1257,1259,1272,1279,1282,1285,1288,1291,1294,1298,1305,1308,1311,1314,1316,1319,1335,1340,1348,1350,1354,1360,1364,1367,1371,1374,1378,1381,1385,1392,1396,1406,1408,1411,1415,1418,1420,1431,1433],[189,1189,1190,1193],{},[196,1191,326],{"href":1192},"https:\u002F\u002Fwww.glean.com\u002F"," is workplace search that grew a work assistant on top. It finds files across Drive, Slack, Confluence, and the rest of the workplace — and it respects who is allowed to see them. Nimbus is the place you then run the job those files imply: update the customer record, file the next step, get a person to sign.",[189,1195,1196,1197,1200],{},"Glean’s centre of gravity is ",[193,1198,1199],{},"find the right object, for the right person, at the right time",". Nimbus’s is a signed-off outcome. Both products will say “knowledge” and “agents.” They are not the same purchase. Search that does not leak is a hard, years-long problem. A release on a live system is a different hard problem. Many enterprises have both. They should not pretend one vendor covers both because both say “knowledge graph.”",[189,1202,1203,1207],{},[196,1204,1206],{"href":1205},"https:\u002F\u002Fwww.glean.com\u002Fproduct","Glean’s product"," connects to Google Workspace, Microsoft 365, Slack, Salesforce, Confluence, Jira, and many more — publicly, 100+ workplace apps — then builds an index that respects the same permissions as the source system. Under the hood that is a mix of classic keyword search and meaning-based search, plus a map of people, documents, and activity. Glean has added assistants and agents so the search layer can also draft and automate. That architecture is why Glean wins large-enterprise search bake-offs. Identity, crawl, and permission fidelity are the hard problems, and Glean has spent years on them.",[239,1209,242],{"id":241},[244,1211,1212,1218,1224,1230,1236,1241,1246,1251],{},[247,1213,1214,1217],{},[193,1215,1216],{},"Workplace search."," An index across the apps the company already uses, so people stop hunting for files.",[247,1219,1220,1223],{},[193,1221,1222],{},"Permission mirroring."," If a document is restricted in Drive, Glean should not surface it in a chat answer. That is the product.",[247,1225,1226,1229],{},[193,1227,1228],{},"Knowledge graph (Glean)."," A map of people, documents, and activity for retrieval. Not the same as Nimbus’s Lifecycle Graph.",[247,1231,1232,1235],{},[193,1233,1234],{},"Crawl."," The programme of connecting apps, mapping identity, and keeping the index fresh. Why IT sponsors Glean. Why it takes time.",[247,1237,1238,1240],{},[193,1239,275],{}," In Nimbus, a shared workspace for one job — not a search result.",[247,1242,1243,1245],{},[193,1244,281],{}," Changing a live system. Search products add agents on top of the index. Nimbus treats the write as a first-class release.",[247,1247,1248,1250],{},[193,1249,291],{}," A causal record of AI work: what ran, who approved it, what changed. Not an index of every file an employee ever touched.",[247,1252,1253,1256],{},[193,1254,1255],{},"Copilot."," Microsoft’s assistant inside Office. Glean searches across many apps, including Microsoft. Neither is a governed execution layer.",[239,1258,302],{"id":301},[189,1260,1261,1262,1266,1267,1271],{},"If you have ever watched a naive chatbot answer from a restricted Drive folder, you understand why Glean exists. Permission mirroring is not a slogan. It is the product: if a document is restricted in Drive, Glean should not surface it in a chat answer. ",[196,1263,1265],{"href":1264},"https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Fsp\u002F800\u002F53\u002Fr5\u002Fupd1\u002Ffinal","NIST SP 800-53 Rev. 5"," Access Control (the AC family) is the control-catalogue reason: the system must enforce who may see what. ",[196,1268,1270],{"href":1269},"https:\u002F\u002Fwww.glean.com\u002Fsecurity","Glean’s security page"," describes that enforcement as a product: permission mirroring, encryption, and compliance claims. Glean is search that does not leak. It is not an AI risk-management framework, and it does not, by itself, put a named signer on a customer-record write.",[189,1273,1274,1275,1278],{},"Glean’s primary object is a document, message, ticket, or person. Nimbus’s primary object is a job, an agent team, a release. Glean’s success metric is time-to-answer. Nimbus’s is time-to-signed-off outcome. Glean’s write path is secondary — agents on top of the index. Nimbus’s write path is first-class: ",[196,1276,1277],{"href":333},"read-only until you open it",", then a person on the change.",[189,1280,1281],{},"Ask whether agents are a feature of search, or search is a feature of agents. Glean is the first. Nimbus is the second. Assistants on a permission-aware index are a reasonable next step for a search company. They still orbit findability. A workstream does not orbit a search result. It orbits a finish line, a budget, and a write policy.",[189,1283,1284],{},"The crawl is why IT sponsors Glean and why it takes time: connecting apps, mapping identity, keeping the index fresh, proving permission QA. That is the right model for a 20,000-person corpus. It is the wrong model if you needed a signed CRM update this quarter and were told to wait until 2019’s files had finished indexing. Nimbus assumes you can already find the policy, or that you will attach the systems this job needs. It does not wait for a company-wide crawl of every historical file.",[189,1286,1287],{},"The two “graphs” are the usual confusion. Glean’s knowledge graph is mostly an index of people and content for retrieval. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms in a vendor meeting is how you buy the wrong one. You can run both graphs. You cannot substitute one for the other.",[189,1289,1290],{},"Role by role, the fork is practical. A CIO running a knowledge programme wants a universal search bar across 100+ apps, with permission mirroring as the non-negotiable. That is Glean. A Head of RevOps wants an agent to propose opportunity updates with a named signer — search will find the deck; it will not be the release. Security cares that Glean does not leak restricted files, and still cares who may change Salesforce. Knowledge workers want time-to-answer. Operators want time-to-signed-off outcome. Legal will not accept “the assistant found it” as the story of why a customer field moved.",[189,1292,1293],{},"A healthy split: Glean for findability across the sprawling workplace; Nimbus for execution on the jobs that mutate systems of record. Do not stretch Glean into an operating layer because it added agents. Do not stretch Nimbus into a crawl of every Confluence page because Perception can answer questions about the record.",[239,1295,1297],{"id":1296},"when-glean-is-a-better-fit","When Glean is a better fit",[189,1299,1300,1301,1304],{},"Choose Glean when the corpus is huge, permissions ",[230,1302,1303],{},"are"," the product, and you need a universal search bar across 100+ apps before you invent agent teams. Choose Glean also if the executive sponsor is the CIO’s knowledge programme rather than a line-of-business operating model.",[189,1306,1307],{},"Deployment is a crawl programme: identity mapping, permission QA, often with Glean or partner engineers in the building. That is the right model for a 20,000-person corpus. Do not treat that implementation cost as a reason Glean is “worse.” It is the cost of doing permission-aware search well.",[189,1309,1310],{},"Do not choose Glean as a stealth agent operating layer. You will spend a year on crawl quality and still lack workstreams, specialist teams, and change control on writes.",[189,1312,1313],{},"Some organisations will run Glean for findability and Nimbus for execution. That is a coherent architecture if you do not pretend one graph is the other. Keep Glean as the place people find the deck. Put the job the deck implies — update the customer record, file the next step, get a person to sign — in a Nimbus workstream. Connectors in Nimbus are not a substitute for Glean-scale historical crawl. A Glean assistant is not a substitute for a quoted write.",[239,1315,368],{"id":367},[189,1317,1318],{},"Search exists inside Nimbus as a way to ask about the record, your playbooks, and the systems you attached. It is not a company-wide crawl of 2019.",[189,1320,384,1321,389,1323,1325,1326,1329,1330,1334],{},[196,1322,388],{"href":387},[196,1324,393],{"href":392}," are scoped per ",[196,1327,315],{"href":1328},"\u002Fproduct\u002Fworkstreams\u002F",". Agents do not get “search everything this user could theoretically open” as the default tool. They get the systems you attached, in the mode you allowed (usually read), until a human releases a write. ",[196,1331,1333],{"href":1332},"\u002Fproduct\u002Fperception\u002F","Perception"," is ordinary language over that scoped world, not a second Glean.",[189,1336,402,1337,1339],{},[196,1338,406],{"href":405},": a workspace, wiki, connectors, a first workstream. You do not wait for an index of every historical file to finish.",[189,1341,410,1342,1344,1345,414],{},[196,1343,39],{"href":413}," and the ",[196,1346,23],{"href":1347},"\u002Fproduct\u002Flifecycle-graph\u002F",[239,1349,418],{"id":417},[420,1351,1353],{"id":1352},"does-glean-require-more-implementation-than-nimbus","Does Glean require more implementation than Nimbus?",[189,1355,1356,1357,1359],{},"Usually yes. Permission-aware crawl at enterprise scale is a programme. Nimbus is self-service for most buyers: you are not waiting on vendor engineers sitting with your team for months to get collaboration, sign-off, and a causal record. That is not a claim that Glean is slow for no reason. Crawl and permission QA ",[230,1358,1303],{}," the work.",[420,1361,1363],{"id":1362},"does-nimbus-replace-glean","Does Nimbus replace Glean?",[189,1365,1366],{},"Only if your Glean usage is a thin Q&A bot on a small corpus. It does not replace Glean as permission-aware enterprise search across a sprawling workplace. If you need the latter, keep a search product.",[420,1368,1370],{"id":1369},"both-mention-knowledge-graphs-are-they-the-same","Both mention knowledge graphs. Are they the same?",[189,1372,1373],{},"No. Glean’s graph is mostly an index of people and content for retrieval. Nimbus’s Lifecycle Graph is an operational ledger of work, agents, and releases. Collapsing the terms in a vendor meeting is how you buy the wrong one.",[420,1375,1377],{"id":1376},"can-nimbus-search-drive-and-slack","Can Nimbus search Drive and Slack?",[189,1379,1380],{},"Connectors bring live systems into agent context and into questions you ask about the record. That is targeted operational retrieval, not a Glean-scale crawl of every historical file. If you need the latter, keep a search product.",[420,1382,1384],{"id":1383},"glean-vs-copilot-vs-nimbus","Glean vs Copilot vs Nimbus?",[189,1386,1387,1388,414],{},"Copilot is productivity inside Microsoft that respects Microsoft permissions. Glean is search across many apps (including Microsoft) that respects source permissions. Nimbus is governed execution. A Microsoft-first company may still need Glean if SharePoint search is not enough, and may still need Nimbus if Copilot Studio is not an operating layer. See ",[196,1389,1391],{"href":1390},"\u002Fblog\u002Fnimbus-vs-microsoft-copilot\u002F","Nimbus vs Microsoft Copilot",[420,1393,1395],{"id":1394},"can-we-run-glean-and-nimbus-together","Can we run Glean and Nimbus together?",[189,1397,1398,1399,1402,1403,1405],{},"Yes. That is the intended coexistence for organisations that have both a findability problem and an execution problem. Do not give Glean agents production write credentials because the index is permission-aware. Permission to ",[230,1400,1401],{},"see"," is not permission to ",[230,1404,670],{},". Route mutations through Nimbus governance.",[420,1407,471],{"id":470},[189,1409,1410],{},"The CIO’s knowledge programme typically owns Glean: identity mapping, crawl, permission QA. Line operators own Nimbus workstreams because they own the systems of record those jobs touch. Security reviews both — leak prevention on the search side, write gates on the execution side.",[420,1412,1414],{"id":1413},"if-glean-has-agents-now-why-add-nimbus","If Glean has agents now, why add Nimbus?",[189,1416,1417],{},"Because agents on an index are still a feature of search. Time-to-answer is not time-to-signed-off outcome. If the job is to change a customer record with a person on the write, you need a workstream, a wiki clause, and a graph — not another way to find the deck.",[239,1419,492],{"id":491},[189,1421,1422,497,1426,505,1429,414],{},[196,1423,1425],{"href":1424},"\u002Fblog\u002Fwhat-is-enterprise-rag\u002F","What is enterprise RAG",[196,1427,1428],{"href":319},"What is a lifecycle graph",[196,1430,1391],{"href":1390},[239,1432,511],{"id":510},[244,1434,1435,1439,1444,1449],{},[247,1436,1437],{},[196,1438,326],{"href":1192},[247,1440,1441],{},[196,1442,1443],{"href":1205},"Glean product",[247,1445,1446],{},[196,1447,1448],{"href":1269},"Glean security",[247,1450,1451],{},[196,1452,1453],{"href":1264},"NIST SP 800-53 Rev. 5 (Access Control)",{"title":169,"searchDepth":170,"depth":170,"links":1455},[1456,1457,1458,1459,1460,1470,1471],{"id":241,"depth":170,"text":242},{"id":301,"depth":170,"text":302},{"id":1296,"depth":170,"text":1297},{"id":367,"depth":170,"text":368},{"id":417,"depth":170,"text":418,"children":1461},[1462,1463,1464,1465,1466,1467,1468,1469],{"id":1352,"depth":542,"text":1353},{"id":1362,"depth":542,"text":1363},{"id":1369,"depth":542,"text":1370},{"id":1376,"depth":542,"text":1377},{"id":1383,"depth":542,"text":1384},{"id":1394,"depth":542,"text":1395},{"id":470,"depth":542,"text":471},{"id":1413,"depth":542,"text":1414},{"id":491,"depth":170,"text":492},{"id":510,"depth":170,"text":511},"Glean is permission-aware workplace search; Nimbus is the place an agent can change a customer record — with a person signing off.",{"eyebrow":555,"title":1474},"Search versus a signed change",[1476,1479,1482],{"question":1477,"answer":1478},"What is Glean for?","Permission-aware workplace search. It finds the file the person is allowed to see.",{"question":1480,"answer":1481},"What is Nimbus for beside search?","The job the file implies: changing a customer record, with a person signing off.",{"question":1483,"answer":1484},"Can search replace the write path?","No. Finding the deck and being allowed to act on it are different controls. Many companies need both.","\u002Fblog\u002Fnimbus-vs-glean",{"title":1182,"description":1472},"blog\u002Fnimbus-vs-glean",[569,1489,1490,1491,1492],"glean","enterprise-search","knowledge-graph","agents","ZPznjefdGfilTWFfVNBL098K-K1ns95GH7UNKbmWFkU",{"enabled":163,"message":1495,"linkLabel":79,"linkHref":80,"id":1496,"title":1497,"archived":163,"authors":164,"badge":164,"body":1498,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":164,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1502,"relatedHeading":164,"seo":1503,"series":164,"sitemap":163,"status":164,"stem":1504,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1505},"We're hiring! Join the team building the Sentient Enterprise.","content\u002Fshared\u002Fhiring.md","Hiring banner",{"type":166,"value":1499,"toc":1500},[],{"title":169,"searchDepth":170,"depth":170,"links":1501},[],"\u002Fshared\u002Fhiring",{"title":1497,"description":169},"shared\u002Fhiring","1zs3boivKda1e-b-hAyuNcmZSKjZUAXmecnwHVgcHzk",{"fold":1507,"id":1511,"title":1512,"archived":163,"authors":164,"badge":164,"body":1513,"date":164,"definedTerm":164,"department":164,"description":169,"extension":172,"eyebrow":164,"faqHeader":164,"faqs":164,"footerBand":1517,"headline":164,"image":164,"industry":164,"jobType":164,"listed":131,"location":164,"navigation":131,"openRoles":164,"pageLayout":164,"path":1521,"relatedHeading":164,"seo":1522,"series":164,"sitemap":163,"status":164,"stem":1523,"subhead":164,"tags":164,"video":164,"whyJoin":164,"workplaceType":164,"__hash__":1524},{"headline":1508,"description":1509,"primaryLabel":8,"primaryTo":1510,"secondaryLabel":593,"secondaryTo":12},"Run frontier AI your business actually owns.","Governed workstreams, 3,000+ integrations, and a proprietary knowledge graph. Start on Free.","\u002Fsignup?plan=free","content\u002Fshared\u002Fcta.md","Site CTAs",{"type":166,"value":1514,"toc":1515},[],{"title":169,"searchDepth":170,"depth":170,"links":1516},[],{"headline":1518,"description":1519,"primaryLabel":8,"primaryTo":1510,"secondaryLabel":1520,"secondaryTo":85},"See what governed AI looks like on your stack.","Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.","Talk to our team","\u002Fshared\u002Fcta",{"title":1512,"description":169},"shared\u002Fcta","eYqahyaPnbp8GKrWpoORbZdtmkWmgHr5F61ZHOnb8sY",1792999485718]