Admins can invite teammates and control what each person can view or manage.
When To Use This
Use users and permissions when finance, fundraising, operations, or leadership teammates need different levels of dashboard access.
Before You Start
You must be an organization admin.
Know which areas the teammate should access before inviting them.
Steps
Go to Settings.
Open Organization.
Select Users.
Invite the teammate by email.
Choose the appropriate role.
Save the change.
Built-In Roles
CharityStack includes these built-in roles:
Admin: full access to all areas, including settings, user management, payments, forms, and elements.
Finance: can manage Contacts, Payments, and Subscriptions, and view Payouts. Finance users cannot manage forms, elements, or settings by default.
Editor: can create and manage forms and elements. Editors cannot access payments, Subscriptions, payouts, or settings by default.
Custom Permissions
Admins can customize Finance and Editor permissions from the Permissions area.
Admins can also create custom roles when a teammate needs a more specific access pattern. Custom roles start with no permissions until an admin configures them. An organization can have up to five custom roles.
If a custom role is deleted, users assigned to that role are reassigned to Editor.
Notes
Give teammates the narrowest role that lets them do their work. Finance users usually need Payments and Payouts. Fundraising users usually need Forms, Elements, Contacts, and Subscriptions.
Admins can also customize role access from the Permissions area when custom access is needed.
The Users area is for managing team members and their roles. The Permissions area is for customizing what each role can access. Billing and organization settings may only be visible to users with the right permissions.
During onboarding, admins may also see an invitation prompt where they can add teammates by email, choose roles, send invitations, or invite the team later.
If a teammate cannot see a page or action, confirm their role first. Then check whether the action needs a more specific permission, such as billing, payouts, payments, forms, elements, contacts, or organization settings.