A new nonprofit employee rarely struggles because the organization has no information.
They struggle because the information is everywhere.
The employee handbook is stored in one SharePoint site. Program procedures are buried in a Teams channel. Technology instructions are in old PDFs. Grant requirements live in spreadsheets. Department expectations are explained verbally. Important exceptions are known only by experienced employees.
During the first several weeks, the new employee must figure out where everything is, which documents are current and whom to ask when the written guidance is incomplete.
This creates an onboarding process built around interruptions.
Managers repeat the same explanations. HR answers routine questions. Coworkers forward documents. New employees wait for help before they can continue working.
Maisy gives nonprofit employees one place to ask questions and retrieve approved policies, procedures, training materials and institutional knowledge.
It does not replace managers, training or human judgment. It makes the organization’s approved guidance easier to find when employees need it.
Onboarding Is More Than an Orientation Meeting
Many organizations treat onboarding as a short administrative process.
The employee completes tax forms, receives a laptop, reviews the handbook and attends several introductory meetings. After that, the employee is expected to begin learning through experience.
But effective onboarding continues long after the first day.
A new employee may need to understand:
- The organization’s mission and programs
- Their department’s responsibilities
- Approval and escalation procedures
- Technology systems
- Information-security expectations
- HR policies
- Grant restrictions
- Program documentation requirements
- Emergency procedures
- Communication standards
- Recordkeeping practices
- Relationships between departments
- Which system contains the authoritative record
- When professional or supervisory review is required
The National Council of Nonprofits recommends giving employees written workplace guidance through an employee handbook or manual. Written policies create a necessary foundation, but employees still need practical help applying those policies to daily work.
A handbook may explain the organization’s leave policy. It may not explain where the request is submitted, who approves it, what employees should do during an emergency or whom they should contact when the system is unavailable.
Policies state expectations. Onboarding must connect those expectations to actual work.
A Realistic Nonprofit Example
Consider a nonprofit with 60 employees operating several programs across three locations.
The organization hires a new program coordinator.
During the first month, the coordinator needs to learn:
- How participant documentation should be completed
- Which program expenses are allowable
- Where approved forms are stored
- How incidents are reported
- Who approves purchases
- How referrals are handled
- Which meetings are required
- How technology support is requested
- Which information may be shared externally
- When a supervisor must review a decision
The employee receives a handbook, a job description and several links.
Some of the links lead to large folders. Several documents have similar names. One procedure appears to have been updated, but the old version remains available. A manager explains that one location follows a slightly different process because of a funding requirement.
The employee begins asking questions.
The supervisor answers what she can. HR handles policy questions. Finance explains purchasing. Technology helps with system access. Experienced program employees explain how work is actually completed.
None of these individual conversations is unreasonable.
The problem is that the organization repeats the same onboarding process every time someone is hired.
Why Nonprofit Onboarding Breaks Down
Information is organized by department, not by employee need
HR organizes HR documents. Finance organizes finance procedures. Program leaders organize program guidance.
A new employee does not necessarily know which department owns the answer.
A question about travel may involve HR policy, finance documentation, grant restrictions and supervisor approval. The employee may need to search several locations before understanding the complete process.
Training depends on manager availability
Nonprofit managers often carry large operational workloads.
They may supervise employees while also managing programs, reporting to funders, handling staffing issues and responding to urgent problems.
Onboarding becomes fragmented because training happens whenever the manager has time.
The employee receives pieces of information over several weeks, sometimes without a clear sequence.
Experienced employees fill documentation gaps
When written procedures are unclear, new employees are told to ask someone who has been there longer.
That may solve the immediate problem, but it creates dependence on individual memory.
Different employees may explain the same process differently. Informal guidance may also continue after the official procedure changes.
Documents are not maintained
An onboarding folder may include policies, screenshots, checklists and presentations created over several years.
Without assigned content owners and review dates, outdated documents remain mixed with current materials.
New employees cannot confidently tell which information to trust.
Training is front-loaded
Employees receive too much information during their first few days.
They are shown systems and procedures before they have enough context to understand why they matter.
Several weeks later, when they actually need the information, they may not remember where it was covered.
TechSoup recommends providing documentation and on-demand training that employees can return to when they need a refresher or when a new staff member or volunteer must be trained.
Onboarding works better when employees can retrieve guidance at the moment of need.
How Maisy Supports Onboarding
Maisy provides a conversational layer over the nonprofit’s approved knowledge.
Instead of searching several folders, a new employee can ask:
“How do I request approval for a program purchase?”
Maisy can retrieve the approved procedure and explain:
- Which form is required
- What documentation must be attached
- Who approves the request
- Which expenses require finance review
- Where the completed request should be submitted
- When grant restrictions require additional review
The employee may then ask:
“Where can I find the form?”
Maisy can direct the employee to the approved document in SharePoint.
The answer should be grounded in the nonprofit’s own information. Maisy should not invent a purchasing process based on general internet knowledge.
SharePoint serves as the primary organized knowledge source. Copilot Studio provides the conversational AI layer. Microsoft documents that Copilot Studio can connect an agent to SharePoint sites and lists and retrieve information available to the authenticated user. The connection does not grant employees additional access beyond their existing permissions.
Maisy becomes the nonprofit-facing product through which employees access that approved guidance.
Pixeldust helps assess, organize, configure, test and support the implementation.
Maisy Does Not Replace Human Onboarding
A knowledge hub cannot replace the parts of onboarding that require people.
New employees still need:
- A relationship with their manager
- Introductions to coworkers
- Coaching and feedback
- Program context
- Cultural expectations
- Supervised practice
- Professional judgment
- Clarification of priorities
- Support during difficult situations
Maisy should handle information retrieval, not human connection.
It can answer:
“What is the procedure for reporting an incident?”
It should not decide whether a serious situation is safe, legal or clinically appropriate.
It can explain:
“Questions involving immediate risk must be escalated to the program director.”
It should not independently evaluate that risk.
The strongest role for Maisy is helping employees find approved guidance and recognize when human review is necessary.
What Onboarding Information Should Be Included?
A nonprofit should begin with material that is useful across many new hires.
Organization-wide information
This may include:
- Mission and organizational overview
- Employee handbook
- Workplace policies
- Organizational chart
- Department responsibilities
- Common terminology
- Technology-support procedures
- Security expectations
- Emergency guidance
- Purchasing and reimbursement procedures
- Leave-request instructions
- Communication standards
Role-specific information
Each position may need access to:
- Standard operating procedures
- Program manuals
- Required forms
- Documentation expectations
- Approval paths
- Training materials
- Recurring calendars
- Reporting requirements
- Common scenarios
- Escalation rules
Location-specific information
Employees working across several sites may need:
- Local contacts
- Facility procedures
- Emergency instructions
- Site-specific schedules
- Equipment information
- Access procedures
- Legitimate procedural differences
Differences should be clearly documented. The system should not assume every location operates identically.
Frequently asked questions
Managers and HR staff usually know which questions every new employee asks.
These questions are a practical starting point for the knowledge hub.
Examples include:
- How do I request time off?
- Who approves purchases?
- Where do I submit expenses?
- How do I report a technology problem?
- Which document is the current policy?
- Who should review a participant complaint?
- Where are staff meeting notes stored?
- What should I do if I cannot access a system?
What Should Stay Outside the Knowledge Source?
Onboarding materials should be separated from completed confidential records.
Appropriate HR knowledge may include:
- Blank forms
- Benefit instructions
- Leave procedures
- Workplace policies
- Contact information
- General employee guidance
Information that may need to remain outside the AI knowledge source includes:
- Completed medical forms
- Payroll records
- Performance reviews
- Disciplinary records
- Background checks
- Accommodation documentation
- Confidential complaints
- Individual personnel files
The same principle applies to program information.
Maisy may explain how an employee should document a participant interaction. The participant’s actual case record should remain in the case-management system.
The source system remains authoritative for individual records and transactions.
Permissions Must Match the Employee’s Role
Not every onboarding document should be available to every employee.
A new program employee may need program procedures, general HR policies and technology instructions. They may not need executive records, confidential board materials or restricted HR guidance.
A supervisor may need access to management procedures that general employees should not see.
Microsoft explains that SharePoint-based Copilot Studio knowledge sources use the signed-in employee’s existing permissions when retrieving content.
That does not remove the need for a permission review.
Before launch, the organization should examine:
- SharePoint group membership
- Site and library access
- Inherited permissions
- Guest access
- Public sharing links
- Restricted HR content
- Management-only guidance
- Former employee accounts
- Temporary access
- Location-specific materials
Users should only see information they are authorized to access.
A knowledge hub makes information easier to retrieve. Poorly configured permissions can therefore make existing access problems more visible.
The Knowledge Must Be Clean Before It Is Useful
Maisy cannot fix unresolved content conflicts by itself.
Suppose the onboarding folder includes two incident-reporting procedures.
One says incidents must be reported within 24 hours. The other says they must be reported before the end of the employee’s shift.
Maisy should not choose which rule the organization intended.
A content owner must determine:
- Which procedure is authoritative
- Whether the other version should be archived
- Which employees the rule applies to
- Whether different programs legitimately follow different requirements
- When the procedure should be reviewed again
The implementation process should identify:
- Duplicate documents
- Outdated procedures
- Conflicting guidance
- Broken links
- Missing forms
- Unclear ownership
- Undocumented processes
- Policies that do not match current practice
Microsoft notes that changes to underlying SharePoint content can be reflected in the connected knowledge source, while changes to a source location or connection may require configuration updates.
That makes content ownership critical. Updating the wrong document does not improve the answer.
Build Onboarding Around Real Questions
The best onboarding knowledge structure is not necessarily a large manual.
It is a set of approved answers connected to the documents employees actually need.
Pixeldust can begin by interviewing:
- Recently hired employees
- Supervisors
- HR staff
- Program leaders
- Finance employees
- Technology support
- Experienced staff members
Useful discovery questions include:
- What confused you during your first month?
- Which documents were difficult to locate?
- What did you repeatedly ask your manager?
- Which procedures were explained verbally?
- Where did written instructions conflict with actual practice?
- Which tasks could not be completed without help?
- What information did you receive too early?
- Which questions still arise after onboarding?
The answers reveal where information access is slowing new employees down.
A Practical Implementation Sequence
1. Choose one employee group
Begin with a role or department that hires regularly or experiences a long learning curve.
Do not attempt to redesign the entire organization’s onboarding process at once.
2. Map the first 30 to 90 days
Identify what the employee must learn during each stage.
Separate immediate first-day requirements from information needed later.
3. Collect authoritative materials
Gather current policies, procedures, forms, training documents and system instructions.
4. Capture unwritten knowledge
Interview managers and experienced employees about recurring questions, exceptions and escalation points.
5. Resolve conflicts
Content owners must approve the correct guidance before it is used by Maisy.
6. Organize the information in SharePoint
Apply clear names, permissions, ownership and review dates.
7. Configure Maisy
Connect the approved sources and define how Maisy should respond when information is unavailable, restricted or requires human review.
8. Test with real employees
Ask newly hired and experienced employees to use realistic language.
Test questions that are incomplete, vague or phrased differently from the document wording.
9. Maintain the content
Assign owners and review schedules for every major knowledge area.
Expected Organizational Benefits
A well-designed onboarding knowledge hub can help a nonprofit:
- Reduce repeated manager questions
- Shorten document searches
- Improve consistency between departments
- Give new employees support between training meetings
- Reduce dependence on experienced staff
- Make current procedures easier to identify
- Improve access to role-specific guidance
- Clarify escalation responsibilities
- Support employees across multiple locations
- Preserve institutional knowledge
- Identify missing or conflicting procedures
- Create a more repeatable onboarding process
This does not guarantee that every employee becomes productive immediately.
Some nonprofit roles require extensive training, supervised practice, licensing, professional judgment or direct experience.
Maisy helps remove unnecessary information barriers so managers can focus their time on those higher-value parts of development.
Give New Employees a Better Place to Start
Maisy helps nonprofit employees find approved policies, procedures, training materials and institutional knowledge without replacing managers or the systems the organization already uses.
Pixeldust works with the nonprofit to understand its onboarding process, identify repeated questions, organize authoritative information in SharePoint, review permissions and configure Maisy around the needs of real employees.
The process begins with discovery: understanding what a new employee needs to know, when they need it, where the approved information lives and who is responsible for keeping it current.
