Resolve administrator invitations and existing donor accounts

A confirmed existing account can receive administrator access. The administrator-creation flows look for a confirmed user with the same email, associate that user, and reconcile school access. Creating a donor account first does not by itself require deleting it or creating a second account.

Compare the exact invited email with the account used to sign in, including different institutional email domains or aliases. Ask an authorized school administrator or support to verify the account association and confirmation before making changes. Resetting the password of a different account will not transfer an invitation or grant permissions. A successful sign-in also does not confirm the required product role or access to a particular campaign, form or event.

Use the intended school's invitation or administrator sign-in link in the intended environment. For a missing invitation, an authorized administrator can use Resend Invite where offered; inspect spam/quarantine and escalate persistent nondelivery with the recipient and time. The success notice confirms the resend action, not receipt in the mailbox. Avoid repeatedly creating administrator records or deleting an existing donor profile to troubleshoot.

If the page is blank, redirects unexpectedly, or lacks the expected signup button, record the actual URL/error and provide the screenshot to support. An inaccessible image in a ticket is insufficient to diagnose the page. Do not infer that school branding or campaign setup must be completed to unlock administrator access.

Volunteer Management staff and volunteer identities have their own flows. Do not assume that a legacy VMS administrator entry triggers the same fundraising/events invitation, or that a volunteer profile must be deleted. Confirm the school's VMS version and supported staff onboarding procedure with support.