Separate administrator roles from campaign, form, event and product access

Check both the permitted action and the objects the administrator may access. Assign suitable roles and the intended individual campaign, giving form or event, and review access groups. Leave the corresponding All Campaigns/All Giving Forms/All Events option off when restricting scope, and remove broader group grants. An all-objects checkbox alone does not grant every action permission.

Basic Campaign Admin includes Edit Campaign: campaign basics, images, video/display, dates/goals and other settings. It can support a teammate editing campaign content without full Superadmin, but it is broader than copy-only editing. Tiered Landing Page Admin adds tiered-page capabilities; combining roles does not restrict the broader role's capabilities. Verify effective access after saving.

The role catalog includes school Superadmin and product-specific Fundraising Superadmin and Events Superadmin. The role-membership flow grants all campaign/form access for fundraising/global superadmin and all event access for events/global superadmin. A long list of individual role selections is not proof of identical effective access. Separate product checks still apply: do not assume that this label unlocks every product. Requested upgrades need an authorized administrator's review.

Event registration deposit reports require View Events Deposit Reports. Events Finance Admin and Events Reporting Admin include that permission in the role matrix; fundraising Finance Admin and Reporting Admin are different roles. Donation deposit access does not confirm event deposit access. If the appropriate Events permission is present and the report remains disabled, support must inspect the live school/account.

Events Check-in Admin includes check-in but not Manage Registrations or Edit Event. Basic Events Admin includes those broader permissions. The matrix does not confirm a role combining only landing-page content, registrant editing and check-in while excluding ticket setup. Ask support to evaluate that precise restriction; do not assume Events Content Manager solves it.

For the Wealth Analytics dashboard, the policy requires the wealth-screening school product and a Wealth Analytics administrator association. Ordinary fundraising administrator status alone does not confirm that access. GC Gift Officer wealth data uses a different permission check, so identify the requested screen before recommending a role.

For a one-form administrator, configure form-specific gift-notification recipients separately and review any schoolwide donation-notification subscription. Object restrictions do not automatically limit notification subscriptions. Do not assume credit-card-only filtering from the form's recipient checkbox or grant schoolwide reporting roles without reviewing the requested scope.