Every nonprofit has questions that get asked repeatedly.
Where is the mileage reimbursement form?
Who approves a purchase over $1,000?
What is the process for requesting time off?
Which version of the volunteer handbook is current?
How should staff respond when a participant makes a complaint?
Where are the instructions for submitting grant expenses?
These are not difficult questions. The problem is that the answers are scattered across shared drives, email threads, policy documents, Teams messages and the memories of experienced employees.
When employees cannot quickly find approved guidance, they ask another employee. That person stops what they are doing, searches for the answer, explains the process and often sends another copy of a document.
The same cycle may happen several times each week.
A secure AI-powered knowledge hub such as Maisy gives nonprofit employees one place to ask routine operational questions and find answers based on approved organizational information.
It does not replace staff judgment or the nonprofit’s existing systems. It reduces the time employees spend searching for information that the organization has already created.
Repeated Questions Are Usually a Knowledge Problem
Repeated employee questions are often treated as a communication problem.
Leadership may tell employees to read the handbook, check SharePoint or search the shared drive before asking for help. That rarely fixes the issue.
Employees may not know:
- Which document contains the answer
- Whether the document is current
- Which folder stores the approved version
- Whether a policy applies to their department
- Which person has authority to answer the question
- Whether an old email contradicts the written procedure
The information may technically exist, but it is not organized in a way that makes it easy to use.
A nonprofit might have detailed purchasing policies, HR procedures and program instructions. If staff must search through several folders and open multiple documents to answer one question, they will usually ask someone instead.
That response is reasonable. The organization has made asking a coworker easier than finding the answer.
A Realistic Nonprofit Example
Consider a nonprofit with 60 employees operating several programs across three locations.
The organization has departments for programs, operations, HR, finance, grants, development, volunteer services and technology.
Over time, each department has created its own collection of documents:
- HR maintains policies and forms in SharePoint.
- Finance stores purchasing procedures in a shared folder.
- Program managers keep instructions in Teams channels.
- Grant requirements are tracked in spreadsheets and email.
- Technology instructions are stored in old PDFs.
- Volunteer guidance exists in several versions.
- Experienced employees answer questions based on memory.
Employees regularly contact HR, operations and finance with routine questions.
A program coordinator asks where to find the travel reimbursement form. A supervisor asks who must approve a vendor agreement. A new employee asks how to request access to a shared system. A department director asks whether a grant allows a specific expense.
Each question may take only five or ten minutes to answer. The cost becomes significant when the same questions are asked repeatedly across the organization.
The larger problem is not just lost time. Different employees may receive different answers depending on whom they ask.
Why Traditional Approaches Break Down
Most nonprofits already have places to store documents. The problem is usually not a lack of storage.
The problem is that storage is not the same as usable knowledge.
Folder structures become difficult to navigate
A folder system may make sense to the person who created it. New employees may not understand where documents belong or which terms to search.
A purchasing policy might be located under Finance, Operations, Administration or Internal Controls. Staff may not know which location is correct.
Search results include outdated files
Employees may find several versions of the same policy.
One file may be labeled “final.” Another may be labeled “final revised.” A third may be attached to an email from two years ago.
Without clear ownership and document controls, employees cannot confidently determine which version is authoritative.
Important knowledge is held by individuals
Experienced employees often know how work actually gets done.
They understand exceptions, approval paths, annual deadlines and informal dependencies that were never properly documented.
When employees rely on one person for answers, that person becomes an operational bottleneck.
Policies do not always answer practical questions
A policy may state that expenses require approval, but employees still need to know:
- Which form to use
- Who approves it
- Where to submit it
- What supporting documents are required
- How long approval usually takes
- Who handles exceptions
The policy establishes the rule. The procedure explains how to follow it.
Both need to be available.
How Maisy Changes the Experience
Maisy gives nonprofit employees a conversational way to retrieve approved internal guidance.
Instead of searching several folders, an employee can ask a direct question:
“How do I request reimbursement for program travel?”
Maisy can retrieve the approved procedure from the organization’s configured knowledge sources and present a concise answer, including the required steps and links to the relevant documents.
The employee might receive guidance such as:
- Complete the approved travel reimbursement form.
- Attach itemized receipts.
- Submit the form to the program director within 15 days.
- Expenses over the established limit require finance approval.
- Questions about grant eligibility must be reviewed by the grants manager.
The answer should come from approved organizational information, not from general assumptions about nonprofit operations.
Microsoft documents that Copilot Studio can use SharePoint sites and lists as knowledge sources. When properly configured, the system retrieves information using the signed-in employee’s permissions, so the employee should only receive content they are authorized to access. Microsoft’s SharePoint knowledge-source documentation explains how authenticated access and SharePoint permissions affect retrieval. (Microsoft Learn)
This does not mean every employee sees every document. Permissions must still be designed and reviewed carefully.
What Information Should Be Included?
The first version of Maisy should focus on common questions that have clear, approved answers.
Useful starting content may include:
- Employee policies
- Standard operating procedures
- Purchasing instructions
- Expense reimbursement procedures
- Technology support instructions
- Approved forms
- Program guidance
- Volunteer procedures
- Grant administration instructions
- Board policies
- Emergency procedures
- Department contact information
- Escalation paths
- Frequently asked questions
The strongest early use cases are usually questions that are asked often, consume staff time and have relatively stable answers.
For example:
- “How do I request new software?”
- “Who approves a new vendor?”
- “Where is the current employee handbook?”
- “What is the process for reporting an incident?”
- “How do I reserve a meeting room?”
- “Who handles questions about payroll?”
- “What is the procedure for onboarding a volunteer?”
These questions do not require the AI to make sensitive decisions. They require the system to locate and explain approved guidance.
What Should Remain Outside Maisy?
Not every piece of information belongs in an AI knowledge source.
Sensitive individual records may need to remain inside the systems specifically designed to manage them.
Examples include:
- Client or participant records
- Medical information
- Payroll details
- Employee disciplinary records
- Donor payment information
- Case notes
- Background checks
- Confidential legal records
- Protected personal information
Maisy should not become a replacement for the nonprofit’s case-management system, donor database, HR system, accounting platform or CRM.
The source system remains authoritative for individual records and transactions.
Maisy may explain the procedure surrounding those systems. For example, it may explain how an employee should request a correction to a participant record. It should not independently alter that record unless a separate, carefully controlled integration has been designed and approved.
Read-only access is usually the safer starting point.
Permissions Must Follow Existing Roles
A knowledge hub does not eliminate the need for information governance.
The nonprofit must decide which employees should access each category of information.
A program employee may need access to program procedures but not confidential HR files. A supervisor may need management guidance that general employees should not see. Board members may require access to governance documents that are not available to volunteers.
SharePoint permissions can help enforce these distinctions, but the permission structure must be reviewed before Maisy is launched.
Microsoft states that SharePoint-grounded Copilot Studio responses use the employee’s authenticated access and do not grant additional permission to restricted content. Employees generally need at least read access to retrieve the underlying information. (Microsoft Learn)
That protection depends on the organization configuring permissions correctly.
A folder labeled “Confidential” is not protected simply because of its name. Access must be restricted technically.
The implementation process should review:
- Existing SharePoint sites and libraries
- Group membership
- Guest-user access
- Broad permission assignments
- Inherited permissions
- Restricted HR and legal content
- Documents shared through public links
- Content that should not be indexed
- Blank forms versus completed confidential forms
Blank benefit forms and general HR procedures may be appropriate knowledge sources. Completed employee forms should remain separate.
The Organization Must Resolve Conflicting Answers
AI cannot resolve conflicts the organization has not resolved internally.
If two documents give different purchasing limits, Maisy cannot determine which policy leadership intends to enforce.
If three departments use different onboarding procedures, the organization must decide whether that difference is legitimate or accidental.
The discovery and preparation process should identify:
- Duplicate documents
- Conflicting instructions
- Missing procedures
- Outdated policies
- Documents with no clear owner
- Unwritten processes
- Information stored only in email
- Questions with no approved answer
This is one of the most valuable parts of the implementation.
The organization is not simply uploading documents into an AI tool. It is establishing which information should be trusted.
Content Ownership Still Matters
Maisy can make approved knowledge easier to access, but it cannot maintain that knowledge without organizational ownership.
Each major content area should have an assigned owner.
HR should own HR policies. Finance should own purchasing and reimbursement guidance. Program leadership should own program procedures. Technology staff should own system instructions.
Content owners should review their information on a defined schedule and whenever a major process changes.
Microsoft recommends reviewing knowledge sources regularly and removing outdated or irrelevant content so agents continue working from current information. Microsoft’s knowledge-source management guidance reinforces the need for ongoing maintenance rather than treating implementation as a one-time upload. (Microsoft Learn)
Maisy improves access to knowledge. It does not remove responsibility for keeping that knowledge accurate.
A Practical Starting Point
A nonprofit does not need to organize every document before beginning.
A focused first implementation is usually more effective.
Start with one high-volume question area, such as:
- HR questions
- Purchasing procedures
- New-employee onboarding
- Technology support
- Program operations
- Volunteer guidance
Then follow a structured process.
1. Collect repeated questions
Ask department leaders which questions they answer most often.
Review support requests, onboarding notes, Teams messages and recurring emails.
2. Identify the approved answers
Locate the current policies, procedures, forms and instructions associated with each question.
3. Resolve conflicts
Determine which documents are authoritative. Archive outdated copies.
4. Organize the content in SharePoint
Use clear naming, ownership, metadata and permission structures.
5. Configure and test Maisy
Test real employee questions, including vague wording, alternate terminology and questions that should require human review.
6. Assign content owners
Define who updates each knowledge area and how often it should be reviewed.
7. Expand carefully
After the first use case works reliably, add additional departments and information sources.
The Expected Benefits
The primary benefit is not eliminating questions.
Employees should still ask for help when situations are unusual, sensitive or unclear.
The goal is to reduce unnecessary interruptions and make routine guidance easier to access.
A well-organized implementation can help the nonprofit:
- Reduce repeated employee questions
- Shorten the time spent searching for documents
- Improve consistency across departments
- Reduce dependence on individual employees
- Help new employees become productive faster
- Make approved procedures easier to follow
- Clarify when human review is required
- Improve confidence that employees are using current information
- Identify missing or contradictory procedures
- Preserve institutional knowledge
The result is not an organization where employees never talk to each other.
It is an organization where experienced employees spend less time repeatedly locating forms and explaining routine procedures—and more time handling work that actually requires their experience.
Building Maisy with Pixeldust
Maisy helps nonprofit employees find approved procedures, policies and institutional knowledge without replacing the systems or people they already rely on.
Pixeldust works with each nonprofit to identify repeated questions, locate authoritative information, organize approved knowledge in SharePoint, review permissions and configure Maisy around a focused operational use case.
The process begins with discovery: understanding where information lives, who owns it, who should access it and which repeated questions are consuming the most staff time.
