The business function responsible for a decision should have authority over the knowledge an internal assistant uses to explain it. Give that owner a practical route to approve changes, restrict their scope and withdraw unsuitable guidance. Assign someone to coordinate the work, and a technical owner to verify that approved changes reach the assistant.
A name beside a document is useful only when that person can make the necessary decision and has time to act. For an internal service owner, the test is whether a changed instruction can travel from a colleague's report to an authorized source and a checked answer. Ownership should make that possible without turning every small correction into a queue for one person.
Assign authority at the level of the decision
A repository administrator may be able to edit every file while having no authority to change a returns procedure. A regional operations lead may know the rule but have no way to update the connected source. Separate those responsibilities before the assistant becomes the place employees go for instructions.
Use the existing business authority for the subject. A folder containing service procedures, purchasing rules and training examples may need several decision owners. It does not acquire one policy owner because one person connected it.
| Responsibility | Decision or work it owns | Evidence of a usable assignment |
|---|---|---|
Business knowledge owner | Approves meaning, applicability and changes within their authority | Can say which source governs, where it applies and when to stop using it |
Content steward | Coordinates proposed edits, reviews, replacement links and unresolved work | Can find the current source and move a reported problem to a decision |
Technical service owner | Maintains the source route and implements permitted access and eligibility rules | Can demonstrate which revision reaches the assistant through an ordinary employee account |
These responsibilities can overlap. Agree a deputy or escalation route for absence, and give the people enough capacity to perform the work. The tools-and-workflows guide places this arrangement alongside ongoing service support.
Keep contributions possible without giving everyone the same authority
Not every kind of knowledge needs the same editing control. The Consortium for Service Innovation's Knowledge-Centered Service guidance distinguishes experience-based articles from compliance-based material. In that framework, a broad community can maintain experience-based knowledge, while designated people or groups control changes to policy, regulatory or legal content. It is a service-management practice, rather than evidence that one approval model fits every AI assistant.
Apply that distinction to your own material. Colleagues may be able to correct an ordinary troubleshooting tip within agreed boundaries. Changing a customer commitment or an operating rule can require someone with different authority. Make proposing a correction straightforward in both cases, including when the employee cannot edit the source.
In an October 2026 Reddit discussion, a user describing a search-marketing agency reported a middle course: colleagues could propose changes, a few people could approve shared instructions, and client-specific feedback went to that client's knowledge base. Asked about testing, the poster said they still approved most changes themselves and expected the process to become more complex as more approvers joined. The agency's size and results were not established. Its useful detail is the separation between contributing an observation and authorizing a wider change.
Decide what happens when a review is due
An approval, an effective date and a review deadline answer different questions. Record them separately where the work needs them, and agree the assistant's behavior before a deadline arrives.
| Source condition | Decision the owner needs to make |
|---|---|
Approved now, effective later | When may answers start using the new instruction? |
Routine review is due | Can the existing guidance remain in use while someone checks it, or does this subject require a hold? |
Applicability or accuracy is unresolved | Which answers must pause, and who can settle the uncertainty? |
Superseded or withdrawn | Where must the source stop serving as current guidance, and what history must remain available? |
Match review to how the information changes and the consequences of getting it wrong. A revised service process needs attention when it changes; a calendar reminder cannot replace that signal. Conversely, a missed routine review date does not itself prove that a stable instruction became false. The KCS guide challenges review performed without demand or a useful purpose. Do not impose a universal monthly audit or automatic deletion rule on every source.
Check what the selected product's labels actually do. Glean's documentation on outdated documents, updated in September 2026, says deprecated documents may still appear in search with a warning symbol. It directs unsharing or deletion to the source application. Marking a source outdated is therefore different from proving that it has left the current-answer route.
An archive may still be needed for historical work. Decide its permitted use and access with the responsible owners rather than deleting material merely to clear a review queue.
Keep a regional change within its approved scope
Suppose Jamie Lee leads customer service at an industrial-parts distributor. The assistant uses a central returns instruction that describes warehouse collection. Alex Morgan, the West branch operations owner, approves a revised local procedure requiring the branch desk to authorize the carrier booking first.
Jamie can report that the current answer omits the local approval step. Alex needs to confirm that the procedure is approved within the branch's authority, when it applies and which central instruction it supplements or replaces. A newer file alone does not establish those decisions. Nor should the assistant extend the West branch change to every region.
Make the relevant boundaries visible in the maintained source:
- Applicability. Identify the branch, audience and work covered by the instruction.
- Decision authority. Name who approved the local rule and who can resolve a question about it.
- Timing and replacement. Identify when the change applies and what previous guidance must stop being used for that scope.
- Unresolved cases. Give employees a route to the responsible person when the source does not settle their question.
A translated copy also needs these decisions. Changing the language does not authorize a different operating rule. Ask the appropriate local owner to verify applicability and meaning, including any differences from the central source, before treating it as the local answer.
Verify one source change through to the answer
The business decision is only part of completion. Ask the technical owner to demonstrate the change through the route employees actually use. A successful upload, a verification badge or a changed document title is insufficient evidence on its own.
For Jamie and Alex's returns procedure:
- Record the authorized change. Keep the approved source revision, applicable branch, timing and expected answer together. Use permitted practice information for testing.
- Check the active source route. Establish that the new revision is available for the affected questions and the old instruction cannot supply an incompatible current answer. Check uploaded copies and connected locations as applicable.
- Try the ordinary questions and a boundary case. Test West branch through an ordinary employee account, in a fresh conversation and an existing one. Check another branch to see whether the local change has spread too far. Inspect the source passages as well as the final wording.
- Close the handoff or hold it explicitly. Record what worked, any unresolved question and who must act. If the authorized instruction is unavailable, route the question to the branch desk instead of letting an old answer stand in for it.
Timing can matter. OpenAI's retrieval documentation says file removal from its vector stores is eventually consistent, so search results may still include removed content for a short period. That is a specific service limitation, not a delay to assume for every assistant. Establish the behavior of your actual route and how affected questions are handled during a change.
If the source is correct but the assistant still gives an unsuitable answer, use the company-answer diagnostic to investigate retrieval and interpretation. Use the human-review guide to make the acceptance checks specific. Keep source authority and answer quality connected without treating either as proof of the other.
Start with one source change that matters to current work. Follow it from the person proposing the correction to the person authorizing it, then to an answer employees can check. The first broken handoff tells you what the ownership arrangement still lacks.
Questions about assistant knowledge ownership
Should IT own all the knowledge used by an internal assistant?
IT should own the technical responsibilities it can perform, including connections, configuration and access controls. The business function with authority over the subject should settle the meaning and applicability of its guidance. One person can perform several responsibilities, but the assignment must include decision authority, capacity and cover for absence. Use the responsibility comparison to find the gap before assigning everything to the repository administrator.
Can everyone contribute without everyone editing approved policy?
Yes. Give employees a clear way to propose corrections and distinguish that from permission to approve a changed rule. Routine shared experience may allow broader editing; controlled instructions may require designated reviewers. Keep contributors informed about the decision so reporting errors remains worthwhile. The contribution boundary explains why an open suggestion route and restricted approval can coexist.
Should an overdue review automatically stop the assistant using a document?
Decide that behavior for the subject and risk before the deadline. A routine review reminder and a date after which guidance must not be used are different controls. A missed review does not prove the content is wrong, while an unresolved high-consequence instruction may need to be withheld immediately. Verify what the product actually enforces; an outdated label may still leave the document searchable. Start with the source-condition decisions.
Does translating a policy approve it for another region?
No. Translation changes the language, while regional approval establishes whether the guidance applies to that location, audience and work. Ask the relevant business owner to verify the meaning, local differences and effective period. Keep a connection to the governing source and a route for questions. The West branch example shows why a local instruction must not silently become the answer for every branch.
What happens when a knowledge owner leaves?
Transfer the decision responsibility, review work and necessary access to an authorized successor or deputy. The technical owner should preserve the source history and verify any changed access or answer behavior. If nobody can approve an uncertain instruction, make that gap visible and route affected questions to the appropriate business authority. A former owner's name or an old approval should not substitute for someone able to resolve the next change.
