A nonprofit employee finds three documents that appear to answer the same question.
One is labeled “final.” Another has a newer date. A third was emailed by a manager and includes instructions that do not appear anywhere else. None of the documents clearly identifies its owner, approval status or replacement history.
The employee may choose the newest file, ask a coworker or follow whichever version seems most complete. That guess can affect program delivery, financial procedures, volunteer supervision, compliance and participant safety.
Finding a document is not enough. Employees need to know whether the organization has approved it.
Define What Makes a Source Authoritative
An authoritative source is the approved location or record the organization recognizes as controlling for a specific type of information.
For an internal procedure, that may be a published SharePoint document approved by the responsible department. For a financial transaction, it may be the accounting system. For participant information, it may be the case-management platform. For a board decision, it may be approved meeting minutes or a signed resolution.
Each important document should identify:
- Its content owner
- Approval status
- Effective date
- Review date
- Intended audience
- Related authoritative system
- Previous version
- Whether exceptions require approval
These details help employees understand not only what the document says, but why they should trust it.
Separate Approved Content From Drafts
Drafts and working documents are necessary, but they should not appear beside approved guidance without clear distinctions.
SharePoint can support document approval processes that separate pending material from published content. Microsoft explains how organizations can require document approval in SharePoint and use Power Automate to update a document’s approval status. (Microsoft Learn)
The nonprofit should determine which types of content require formal approval. A temporary event checklist may need a simpler process than a safeguarding policy, financial-control procedure or participant eligibility rule.
The purpose is not to create unnecessary bureaucracy. It is to retain institutional knowledge in a way that distinguishes approved guidance from ideas, drafts and historical records.
Direct Employees to the Source Through Maisy
Once authoritative information is identified and organized in SharePoint, Copilot Studio can provide the conversational layer.
Through Maisy, employees could ask:
- Which version of this procedure is approved?
- Who owns this policy?
- Has this form been replaced?
- Where is the authoritative record?
- Is this document still in effect?
- Who can approve an exception?
Microsoft’s current guidance explains that when SharePoint is added as a Copilot Studio knowledge source, authenticated employees can access permissible SharePoint content through the agent without receiving additional permissions. (Microsoft Learn)
Maisy should direct users to the approved source rather than attempt to reconcile unresolved drafts independently.
Keep Each System’s Authority Clear
The Knowledge Hub should not become the official home for every type of record.
The CRM remains authoritative for donor information. The case-management system remains authoritative for participant records. Accounting software remains authoritative for transactions. HR and payroll systems remain authoritative for employee records. Signed contracts remain authoritative for legal obligations.
SharePoint should contain approved guidance explaining how employees use those systems, along with links to the appropriate records.
The National Archives notes that whether a document is an original or a copy does not by itself determine its record status. What matters is whether it belongs to the official recordkeeping process. Its records-management basics provide a useful framework for distinguishing official records from convenience copies. (National Archives)
Maisy should not decide which disputed document becomes authoritative, approve policy changes or interpret legal requirements. Content owners, leadership and qualified professionals remain responsible for those decisions.
How Maisy Helps
Pixeldust begins by identifying the questions employees ask when they cannot determine which document to follow. Discovery locates duplicates, email attachments, local copies, missing approvals and procedures that conflict with records in operational systems.
Pixeldust then works with responsible leaders to identify authoritative sources, assign content owners, establish approval rules and organize published guidance in SharePoint. Permissions are reviewed before Maisy is configured through Copilot Studio.
Realistic questions are tested to ensure employees receive the approved source and are directed to a responsible person when the organization has not yet resolved a conflict.
This helps the nonprofit retain institutional knowledge while replacing document guesswork with clear ownership, approval and searchable access.
