Logging in, completing two-factor verification and gaining access to a product are separate steps. If the destination is wrong, record the school/unit, intended product, login method and final URL without including credentials or private tokens.
The Online Giving admin base redirects to onboarding if the selected school is neither partnered nor VMS-active in the check. Support should verify the correct school and actual product/setup state; clearing browser cache does not alter those stored values. Do not repeat onboarding for an existing school merely to escape the page.
A volunteer record must be associated with an eligible user. The matching path uses a confirmed non-guest user with matching email; deactivated, read-only and VMS test-environment conditions affect linking. An existing donor account is not inherently incompatible with volunteer access, and creating another account can make reconciliation harder. Support must verify the actual identity-provider identifier and volunteer association when SSO lands on a donor profile or wrong unit. Email aliases that receive the same mail are not automatically interchangeable identity-provider records.
After two-factor verification, stored return destinations and role/school context influence the next page. If you reach an invalid address after verification, send Support the page address and exact error without private tokens. Do not treat every address-not-found page as an invalid code.
The school staff/SSO login component includes a fixed donor-login link reading Looking to make a gift or join a campaign? Log in here. Contact Support if you need to change this sign-in screen. Direct volunteers to the intended SSO entry point and raise UI-change requests with support rather than invent a setting.
Stripe Link is payment authentication, not volunteer sign-in
GiveCampus account/volunteer sign-in is distinct from Stripe Link payment authentication. Stripe Link can appear in eligible checkout; that is not the volunteer login method. Use the institution’s GiveCampus sign-in/SSO route, and have support review an unexpected Link prompt rather than entering payment credentials as account recovery.
Comments
0 comments
Please sign in to leave a comment.