--- title: Charity OS group: For nonprofits and funders order: 20 summary: Coordinate programs, grants, people and learning in a shared organization workspace, or start with a private browser notebook. status: live statusNote: Shared accounts and 26 typed modules, plus the smaller local workspace below. Live software does not imply accounting certification or independently verified impact. conditions: [fragmentation, missing-feedback-loop, measurement-gap, missing-voice] review: draft help: - Try a real program plan using program-level records, and report where the workflow gets in your way. - Propose a clearer way to connect what a team does with what the people affected say changed. - Test a JSON export in another browser and report any field that does not carry over. related: [/tools/impact-measurement-toolkit/, /tools/grant-evaluator/, /tools/due-diligence-checklist/, /record/encyclopedia/theory-of-change/] --- ## Work together [Open the shared Charity OS](https://os.charitology.org) to create an organization and invite your team. Its 26 modules connect programs, projects, grant seeking and delivery, budgets, contacts, volunteers, events, evidence, governance and documents. Roles and optional program assignments control access. Record ownership names responsibility; it does not grant permission. Keep working drafts, comments and decisions together. Another authorized reviewer must approve a revision before it can become an approved snapshot. Board and external readers see permitted approved snapshots. Frozen reports retain the source revisions and a checksum so later edits do not quietly rewrite a past report. The shared service also has a grant-period report workflow. Select one agreement, one program and a period; prepare approved sources, save their versions for separate approval, then preview and freeze an immutable report. Awards, external receipts, spending references and planning remain distinct. Unknown amounts stay unknown, and observations retain their units and limits without becoming causal claims. An eligible board reader receives a separate approved projection rather than private source records. This does not certify accounts, submit a funder report or establish actual human review of test records. Read-only CiviCRM, OpenProject, Kobo and CSV connections have an explicit preview before import. Configure your own credentials; a connection is not automatic two-way synchronization. Files, revision checks, recoverable trash and private JSON backups support handover and recovery. Original import archives can be downloaded separately. Personal reminders run in the daily dispatch after their due time. Accounting records hold external references and reconciliation controls. The OS does not post a ledger, run payroll, move money or issue tax receipts. Casework and safeguarding hold opaque codes and specialist-system references rather than private case narratives. The shared service also supports public operational requests. Approved, version-bound forms can collect minimal contact, event-interest and volunteer-interest requests with explicit consent. A private receipt checks status or withdraws the request; an administrator separately reviews it before preparing unapproved drafts. Sending a request does not book a place, assign a volunteer or subscribe to a newsletter. Answer erasure is separate from withdrawal and cannot remove earlier backups or separately prepared contacts. Restored forms and receipts remain inactive. Controlled checks used synthetic requests; real participant use and actual human review are not implied. [Your requests](https://os.charitology.org/participant) provides separate account access to requests you explicitly link. Both a matching verified email and the saved private receipt are required. Review your own submitted answers, correct eligible pending answers with fresh consent, withdraw, erase answers or permanently unlink account access. Signing in alone searches no requests and grants no team role. Backup imports restore no participant access. The Participation console adds explicit confirmation and waitlists for one place per event session or volunteer shift. A reviewed interest request reserves no capacity. Staff must enable the occurrence, associate the typed candidate and obtain specific consent before confirming a place. Promotion is manual. Confirmed capacity stays reserved through later review edits, and cancellation releases it once. Your linked request can show your own participation and let you cancel it; withdrawing the original request alone does not cancel a confirmed place. Operational email requires a separate fresh choice from the verified participant. An administrator reviews current confirmations before activating delivery; old preferences and paused history are never mailed automatically. The fixed notice links to the signed-in portal without putting occurrence details or receipts in email. Delivery runs in a bounded daily dispatch, so it is not an urgent or exact-time alert. Turning updates off, erasing answers or unlinking access stops unsent updates; a message already attempted may still arrive. Broader workflows and operational acceptance remain in the [implementation plan](/for-charities/os-plan/). ## Start with the local workspace Write down your mission and the community's role in shaping it. Add each program or project with its intended change, owner, budget, spending and target date. Depth is an optional working description, from relief to source. It does not grade the work, and unknown can stay unknown. The grant pipeline keeps opportunities, stages, amounts, deadlines and next steps together. Link a grant to a project, assign an owner, then turn the next step into a task. The dashboard separates pending requests, awards and project budgets so the same money is not quietly counted twice. ## Keep the feedback loop visible The evidence log records what was observed, when, in what units and with what support. It can hold outputs, outcomes, no change and harms. Leave the value blank when it is unknown; zero means an observed zero. Use the notes and source link to explain the method and its limits. A change after a program is not by itself proof that the program caused it. The [Impact Measurement Toolkit](/tools/impact-measurement-toolkit/) helps make that distinction. Every record can be edited or deleted. Deleting a project keeps its grants, tasks and observations without a project link. Undo restores the previous workspace until the next change or reload. Search, project filters and status filters help find what needs attention. ## Keep a copy of your local work The smaller workspace on this page saves only in this browser. Owners are labels for organizing the work, not invitations or notifications. It does not send reminders or submit grant applications. Export **JSON** to keep all fields and restore the local workspace on this or another device. The shared OS can also preview this local file and convert its records into drafts in an empty organization. It preserves the original file privately; owner labels do not become accounts, and observations do not become verified measurements. Import validates the whole file and shows a preview before replacing anything. **CSV** gives you the records for a spreadsheet; use JSON for a full restore. The fictional example is clearly marked and replaces your current workspace only after confirmation when there is existing work. If browser storage is blocked or full, the workspace keeps working on the open page and shows a notice to export before leaving. Clearing browser data removes the saved copy. Use program-level records, and keep private case files in the systems your organization uses for them.