Can a Nonprofit Use AI to Preserve Board Decisions Without Giving Every Employee Access to Board Records?

Yes. A nonprofit can preserve approved board decisions in a Knowledge Hub and make selected operational guidance available through an AI assistant without exposing every board document to every employee. The key is separating confidential governance records from approved organizational decisions, applying role-based permissions before AI retrieval, and assigning a human owner to determine what information may be published for staff use.

Board Knowledge Often Disappears Into Meeting Records

Boards make decisions that shape how nonprofits operate for years.

They approve policies. Establish authority. Change programs. Set strategic priorities. Authorize major purchases. Accept risks. Delegate responsibilities.

The formal evidence may exist in meeting minutes, resolutions and board packets.

But employees rarely search years of board minutes when they need to understand why a process works a particular way.

Instead, institutional memory takes over: “I think the board changed that two years ago.” “Sarah remembers why we stopped doing it that way.” “There was something about this in a board meeting.”

That is how governance decisions gradually become organizational folklore.

Preserve the Decision Separately From the Conversation

A board packet may contain information that ordinary employees should never see.

It might include executive compensation, legal advice, personnel matters, donor information, financial projections, negotiations, risk discussions or confidential strategic alternatives.

Employees may nevertheless need to know the operational result of a board decision.

For example: “Effective September 1, purchases above $10,000 require executive-director approval under the purchasing policy approved by the board on July 15.”

That approved operational statement can be published to the appropriate employee audience without exposing the board’s entire discussion.

The Knowledge Hub should therefore distinguish the governance record from published organizational knowledge derived from that record.

Keep the Original Governance Record Authoritative

Board minutes and signed resolutions should remain in the nonprofit’s controlled governance repository.

The National Council of Nonprofits’ governance resources emphasize the importance of board records and governance practices, including maintaining minutes of board and authorized committee meetings.

The IRS likewise identifies board minutes among records that may be requested during an exempt-organization examination.

Maisy should not replace those records.

Instead, the Knowledge Hub can contain approved summaries or resulting policies that link back to the authoritative governance source for authorized users.

Do Not Treat Every Meeting Note as a Decision

A board member suggesting an idea is not the same as the board adopting it.

A draft resolution is not an approved resolution.

An executive director’s recollection is not necessarily the official record.

A Teams conversation about a board meeting is not the board’s action.

AI cannot safely infer that distinction from similar-looking text.

The nonprofit must explicitly identify approved governance sources.

Create a Board Decision Register

A useful Knowledge Hub component is a controlled decision register.

Each approved record might contain decision title, date, governing body, decision type, approved operational summary, affected programs, effective date, responsible executive, related policy, superseded decision, confidentiality classification, staff visibility, authoritative minutes or resolution and next review date.

Employees could then ask: Who can approve this expense? When did this policy change? Which program did this decision affect? What authority was delegated to managers? Is this still the current policy? Who owns this decision now?

Maisy retrieves the approved organizational answer rather than searching every historical board document indiscriminately.

Design Permissions Before Connecting the Agent

Board information is an obvious example of why permissions cannot be an afterthought.

Microsoft’s Copilot Studio guidance for SharePoint knowledge sources relies on authenticated user access. A practical model might include separate groups for board members, executive leadership, Finance, HR, program leadership and general employees.

The AskMaisy security and permissions architecture applies the same principle: an AI agent should not become a shortcut around the organization’s existing security model.

Source permissions should be corrected before the agent is connected.

Separate Content Ownership From Technical Administration

IT should not decide what a board decision means.

The SharePoint administrator may create the library. The Copilot Studio administrator may configure Maisy. Neither should independently translate a complicated board discussion into official organizational policy.

An appropriate business owner—perhaps the executive director, board secretary, governance committee or another designated role—should approve what becomes published knowledge.

Technical administration controls the system.

Governance ownership controls meaning and authority.

What Should Maisy Say When the Evidence Is Unclear?

Consider this question: “Can our program director sign this contract?”

Maisy finds an old policy granting directors signing authority and a newer board resolution that appears to change the limit.

It should not choose.

A safer response would explain that the available approved sources appear to conflict, cite both sources where the employee has permission, and identify the person authorized to resolve the issue.

The same rule applies when minutes are missing, a decision has no effective date, a policy was never formally approved, the user lacks access to supporting evidence, a later decision may supersede an earlier one, or legal interpretation is required.

Maisy should recognize the boundary of its authority.

Test With Different Personas

Testing should include more than an administrator account.

Try realistic personas: general employee, program manager, Finance employee, HR employee, executive director and board member.

Ask each persona questions that cross permission boundaries.

Then test citations.

An answer may appear harmless while its citation exposes a confidential file name, document location or underlying source.

The AskMaisy human-service nonprofit guide illustrates the broader model: approved operational knowledge becomes easier to retrieve while sensitive program information and professional decisions remain appropriately controlled.

Where Maisy Fits

Pixeldust is the consulting and implementation company.

Its process is Understand, Organize, Empower.

Pixeldust first identifies where governance knowledge resides, which decisions employees actually need and who has authority over those decisions.

The Knowledge Hub becomes the governed collection of approved organizational knowledge.

Maisy provides the employee-facing conversational interface.

A typical implementation may use SharePoint, Microsoft 365, Teams, Copilot Studio, Entra ID, Power Automate and Microsoft Purview.

Maisy should usually provide read-only guidance. It does not vote, approve policy, interpret legal obligations, override management or turn confidential board deliberations into employee knowledge.

The goal is simpler: preserve the decisions employees legitimately need without opening the boardroom filing cabinet to everyone.