One login. Access that stops exactly where it should.
A year of people arriving and leaving, with access that follows the hierarchy
The state office invites its own staff
Each person is invited by email at the state level. They get an onboarding email, set a password or use the FutureFund account they already have, and can see every district, council and unit in the state.
A district invites its council leaders
The district opens its Team page and invites the people who run each council under it, at the council level. Each one sees their council and its units, and nothing beside it.
June: a unit's new president is invited
The outgoing president, or the council, invites the new one at the unit level. They accept, and they see that one unit: its tasks, its documents, its board, its messages.
The invitation that was not answered
Pending invitations are re-sent automatically. One that bounced is flagged, so an invitation to a dead address is not silently lost. The Expired Team Invitations report lists the ones never accepted.
An auditor gets a viewer seat
Somebody who needs to look but must not change anything is invited as a viewer. They can read everything at their level and below, and cannot edit, submit or send.
One person, three organizations
A treasurer at one unit who also serves on the council is on both. The same login, and My Organizations switches between them.
The same login opens FutureFund and BeeKeeper
A unit that fundraises on FutureFund and keeps its books in BeeKeeper signs in once. Connect, FutureFund and BeeKeeper share one FutureFund account.
The roster and the team stay separate
The board roster is who holds each position. The team is who signs in. A treasurer on the roster does not need a login unless they administer the unit, so the board is complete without everyone having an account.
Access has to match the hierarchy, and it has to survive turnover
A shared drive is either open to the whole state or locked down to the office. Neither is what a council leader who needs her twelve units actually needs.
The unit's login belonged to the person, not the unit. She moved in June, and the new president is emailing the state office asking how to get in.
A volunteer who already signs in to FutureFund to run the fall fundraiser should not need a second username to file the unit's financial report.
How a person is let in, and how far they can see
Whether you can change what you see is the second setting, member or viewer, and the person who invited you chooses it.
The right people in, at the right level
Built for state PTAs and school districts. We set it up with you.
What every office gets
Who has access to this organization, at what level of access, and whether they have accepted yet.
Invite by address. The person sets a password or uses their existing FutureFund account, and is in.
A person sees their level and everything below it. The state sees all of it.
A seat that can look at everything and change nothing, for auditors and incoming officers.
Pending invitations are re-sent, bounced ones are flagged, and a report lists the ones never accepted.
The same account signs in to Connect, FutureFund and BeeKeeper, and switches between every organization a person is on.
And so much more
Frequently Asked Questions
Keep looking around
Directory & Search
A directory of every district, council and unit under you, with its status, its board and its documents. Search across the whole hierarchy, star the ones you visit most, export any tab to Excel.
Compliance Reports
A compliance report for every level: which documents are in, which tasks are past due, what the IRS and the state charity registry say about each organization. Filtered, sorted, exported to Excel.
Tasks & Approvals
Required tasks are created on a schedule you set, assigned to the unit, council or district that owes them, and routed up for approval. Weekly reminders chase what is past due, so your office does not have to.