Web Dashboard
Use the dashboard to set up Givebear, structure fundraising, manage money, work with people, and administer the organization.
The dashboard is the private workspace for staff and admins. It is where you decide what donors see, how money is routed, who can access the organization, which add-ons are enabled, and how day-to-day fundraising work is tracked.
This section is written as an operating manual. It explains the concepts first, then points you to the guide that answers the next question.
How do I launch?
How should I structure fundraising?
How does money move?
How do I manage people?
How do events and kiosks fit in?
How do permissions work?
The dashboard model
Givebear has a small set of objects that show up across many pages:
| Object | What it means | Use it when |
|---|---|---|
| Organization | The workspace, billing account, Stripe context, brand, members, and add-ons. | You are configuring how Givebear works for the nonprofit. |
| Fund | A donation destination. | Donors should give to a specific bucket such as General Fund, Zakat, Building Fund, or Youth Program. |
| Campaign | A time-bound or story-led appeal. | You want a landing page around an urgent need, season, goal, or donor message. |
| Transaction | A payment event and its financial summary. | You need accounting detail, refund state, dispute state, fees, or net amount. |
| Contact | A person record. | You need donor history, outreach, tasks, tags, segments, or CRM-style follow-up. |
| Event | A registration and attendance workflow. | You need ticket types, forms, registrations, check-in, and attendee reporting. |
| Device | A physical kiosk. | You accept in-person card-present donations and need sync, logs, screenshots, or remote actions. |
Start with the question, not the page
I need donors to give online. Start with Getting Started, then Fundraising Guide.
I need finance answers. Start with Donations and Finance. Use transaction-level records for accounting detail and Reports for summaries.
I need to invite staff. Start with Settings, Roles, and Billing. Do not make everyone an admin just to unblock a workflow.
I need a public calendar, prayer times, or event list. Start with Events and Community, then Widgets if the output needs to appear on a website.
I need a developer to embed Givebear. Start with Widgets for product context, then SDK for method names and configuration.