Setting Up Student Logins and Emails in GC GO – GiveCampus University

A decision guide for student managers

Before your students make a single call or send a single email, you’ll make two setup decisions. They’re easy to lump together, so here’s the most important thing to know up front: how a student logs in and which email they send from are completely separate choices. They don’t have to match, and you decide each one independently.

The login	The GiveCampus account a student uses to get into GC GO.
The connected email	The address GC GO sends from when that student emails a constituent.

A student signs in with one and sends from the other. Once you treat these as two separate questions, the rest of the setup gets a lot simpler. Let’s walk through each.

Decision 1: How students log in

Every student needs a GiveCampus account to access GC GO. You have two ways to set those up.

Option A — Individual logins. Each student logs in with their own personal .edu email address. The student manages their own login and completes the email connection step. When a student leaves, you inactivate that user and create a new one for the next student.

Option B — Generic, school-managed logins. You create generic GiveCampus accounts (e.g., Student1@school.edu), one per seat. The school owns the credentials and hands them to whoever fills that seat. When a student leaves, the school resets the password and gives it to the next student.

	Individual logins	Generic logins
Who manages the login	The student	The school
When a student leaves	Inactivate the user, create a new one	Reset the password, hand it to the next student
Tracking individual activity	Easy — tied to a named person	Harder — rolls up to a seat
Account upkeep	More	Less

The bottom line: Individual logins make it easy to see exactly who did each piece of outreach. Generic logins mean less set up — especially if you sync contact report data back to your CRM. Every GC GO user has to map to a CRM ID if you’d like contact reports to sync back to your CRM, so with individual logins you’re syncing back to a new ID every time a student turns over. With generic logins, you map a fixed set of users once and reuse them as students cycle through.

Decision 2: Which email students send from

This is the address GC GO uses to send to constituents — and to receive their replies — when a student emails them.

ONE RECOMMENDATION FIRST

We don’t recommend connecting students’ personal .edu emails for outreach, for two reasons:

• A personal inbox can’t be auto-forwarded to a manager, so you lose that visibility if you want it.

• Nothing stops a student from emailing constituents, or receiving their replies, after they’ve left your engagement center.

Instead, have IT create dedicated outreach emails. You have two ways to do it.

Option A — Individual emails per student. IT creates a unique address for each student user (e.g., StudentCaller_Name@school.edu).

Option B — Generic, reusable emails. IT creates shared addresses (e.g., StudentCaller@school.edu) that get reused as students come and go.

	Individual emails	Generic emails
Example	StudentCaller_Name@school.edu	StudentCaller@school.edu
Feel for the constituent	More personal	More generic
IT lift	A new address per student	One-time setup, then reused
When a student leaves	Retire the address	Hand the same address to the next student

The bottom line: Individual emails feel more personal — constituents see a real name on the other end. Generic emails mean less work, since they’re typically a one-time setup for your IT team with nothing new to build each time a student joins.

Putting it together

Because login and email are independent, you can mix and match. The two most common setups:

Maximize personalization & tracking

Individual logins + individual emails. More setup and upkeep, but you can see exactly who did what, and constituents get a named human.

Minimize ongoing work

Generic logins + generic emails. A little less granular, but your IT team and CRM mapping are largely set-and-forget as students turn over.

There’s no wrong answer. It comes down to how much you value individual tracking and personalization versus how lean you want to keep setup and maintenance — and plenty of teams land somewhere in between.

Want help thinking through which setup fits your program? Your Partner Success Manager is glad to talk it through.

Related to