Givebear LogoGivebear

Settings, Roles, and Billing

Invite the right people, assign permissions, manage billing, and protect organization-level settings.

Settings are where small mistakes have wide effects. Use this guide before inviting staff, assigning admin access, changing public identity, editing billing, or enabling add-ons.

Organization settings

Organization settings describe the workspace and public identity. Depending on the page, staff may manage:

  • Name and public slug.
  • Logo and accent color.
  • Contact email.
  • Website and address details.
  • Domain or public page settings.
  • Danger-zone actions.

Treat the public slug and contact email as donor-facing values. A finance lead may care about legal and billing information, while communications staff may care more about brand and public presentation.

Roles

Givebear has built-in roles and custom role support through Better Auth DAC.

RoleUse it forBe careful with
OwnerThe person ultimately responsible for the organization workspace.Owners should be rare.
AdminTrusted staff who manage broad configuration and sensitive workflows.Do not use admin access just to let someone check in event attendees.
MemberStaff or volunteers with narrower access.Members may need custom permissions for specific workflows.

Role templates shown in the app include Financial Manager, Event Manager, Campaign Manager, Communications Manager, and Analyst. Use templates as a starting point, then review the exact permissions.

Permission areas

Permissions are grouped around the work they protect:

  • Organization settings.
  • Members and invitations.
  • Roles and permissions.
  • Campaigns.
  • Events.
  • Funds.
  • Donations and transactions.
  • Donors and contacts.
  • Devices and kiosks.
  • Billing and payments.
  • Analytics and reports.
  • Marketing.
  • Features and add-ons.

When someone asks for more access, ask what job they need to complete. Grant the smallest access that covers that job.

Billing

Billing controls the Givebear plan and platform subscription state. It also affects whether the organization can accept payments.

PlanBilling readiness rule
FreeReady after the plan is selected.
PlusRequires an active or trialing platform subscription.
GrowthRequires an active or trialing platform subscription.

Billing pages should be used to review subscription state, invoice details, plan changes, included usage, and overage context. Do not use stale screenshots or copied plan text as the source of truth.

Add-ons

Add-ons enable specialized features such as prayer times, Ramadan campaigns, church services, community calendars, holiday giving, temple events, and volunteer workflows.

Turn on add-ons when the organization has a real operating need. Turning on every add-on makes the dashboard harder to understand and can confuse staff training.

Admin checklist

Before changing settings, roles, or billing, confirm:

  1. The requester has authority to make the change.
  2. The change affects only the intended organization.
  3. Any public-facing text is donor ready.
  4. Billing changes are understood by the finance owner.
  5. Permission changes match the person's job.
  6. Add-on changes are documented for staff who use that workflow.

On this page