Members and roles
Last reviewed
Open MembersCommon tasks and related guides
Roles overview
Every person in your co-op has one primary role. Roles control what they can see and do inside the app:
Owner
Full access to everything, including billing, audit logs, and ownership transfer. Only one person can be the owner at a time. The owner is usually the co-op director or primary coordinator.
Admin
Can manage most co-op operations. By default an admin sees everything and can change most settings, but you can scope their access to specific areas using granular permissions (see below). A co-op can have multiple admins.
Teacher
Can view their class rosters, take attendance, enter grades, and create assignments. Teachers don’t see billing, member lists, or admin settings. A person can be both a family member and a teacher at the same time.
Family
The default role for co-op families. Can browse classes, enroll students, view the Families page, use the forum and community pages, and manage their own profile. No access to admin tools.
Adding members to your co-op
Families and first-time teachers can come in through your join link and an application. A separate Invite tool on Admin › Members lets you add someone directly (Admin, Teacher, or Family) and skip the queue.
The Members list itself shows each person’s photo or initials, name, role, and how long ago they last used HomeschoolGo, so you can spot an account that’s never signed in at a glance. Use the search box to find someone by name or email, the role and status filters to narrow the list (for example, everyone who’s never signed in), and the sort control to order by role, name, join date, or last active.
Test Co-op
Menu › Admin Dashboard › Members
Members
Invite a memberDana Owner
dana@example.com
Sam Teacher
sam@example.com
Alex Sample
alex@example.com
Application flow (how most people join)
Share your co-op’s join link (found at the top of Admin › Applications). Anyone who clicks it submits an application you review before approving. This is how new families and first-time teachers usually join, and it’s required if you charge a join fee, since the fee is collected automatically when you approve.
Direct invite
Go to Admin › Members and click Invite a member. Enter one or more email addresses (press Enter or a comma after each one, or paste a whole list at once) and choose a role: Family, Teacher, or Admin. No role is picked for you, so you choose one for each invite. It works either way: if the address already has a HomeschoolGo account, that person is added to your co-op in the role you picked right away; if it doesn’t, an account is created for them and they get an email to set it up.
When you invite one address, you can also type the person’s Name. It’s optional, and it’s only used when a new account is created. Someone who already has an account keeps the name they chose. Staff without a family in your co-op can add or change their own name under Profile › Your name.
If that setup email doesn’t land (a typo in the address, a spam filter), the member is still added, but they have no way in until they get a link. Reopen their Member actions menu on Admin › Members and look for Resend invite. It only appears for someone who has never signed in, and it sends a fresh setup link (the original link only works once, so forwarding an old invite email won’t help).
The invite email has a Set up your account button. It opens a page where the new member clicks Continue to sign in. If the link has expired or was already used, that page offers Email me a new link instead, and a fresh one goes to the address you invited, so they don’t have to ask you to resend it.
When the email was rejected outright, the Members page says so. If the most recent invite to someone who has never signed in came back as undeliverable, their row carries an Invite bounced badge and a line naming the address it was sent to. That is usually a typo. Resend invite still appears, but it goes to the same address, so check the spelling first and invite the correct address if it’s wrong. A mailbox that was only full or busy for a while doesn’t trigger the badge.
A Require a membership application checkbox controls whether they fill out your standard join form (contact details, any children, your waivers) before using the rest of the app. It’s always on for the Family role, since a family membership with no children or waivers on file isn’t much of one; it’s optional and off by default for Admin or Teacher, useful when you want a paper trail for a board member or a teacher with no kids in the program. Either way, their role and access start immediately. The checkbox only controls whether they’re routed to the join form until they submit it.
Missed the checkbox, or added someone before it existed? The same request can be made later: Require membership application in their row’s Member actions menu flags their account, emails them, and routes them to the form as themselves the next time they sign in. There’s no link to forward, so nothing can mix up their application with your account. This is also how an existing teacher or admin ends up with a payment record: once their application is approved, any join fee applies to them the same as any family (unless your term settings waive it for staff), and you can apply credits to them from Payments.
If someone already filled out the form in the past, that option won’t appear. There’s nothing left for them to submit. Use Add as a household instead. Staff with no children have no household, and a household is what the start-of-term review attaches to, so until they have one they’re never asked to sign your waivers, and there’s nothing for a charge or credit to land on. Adding one fixes both: the next time they sign in they’re asked to confirm their details and agree to every waiver they haven’t signed, the same as any family, and the current term’s join fee applies if one is due. It shows for anyone who doesn’t have a household yet, and if they’re already on one (a spouse’s, for instance), it says so rather than creating a second.
A parent can end up in the same spot. The join form decides whether an applicant is a family or a teacher by whether they list any children, so a parent who leaves that section blank is filed as a teacher and comes out the other side with no household. On their row the option reads Create their household, and it makes a normal family record that shows in your directory like any other. Add their children to it from Families, or leave it to them at their next sign-in. If they haven’t applied at all, use Require membership application instead: the form collects their children and waivers in one pass, which this doesn’t.
A third way records land in your roster is a CSV import of your old records. On Admin › Settings, the Import tab walks you through uploading an export from Homeschool-Life.com yourself: a preview screen shows how many families and students it found before anything is created, and a family already on file (matched by email) is skipped automatically rather than duplicated. Those families show up in the directory right away, but each one carries a Not yet activated badge until a parent signs in and goes through their term’s Confirm your information review. That first sign-in is what turns an imported record into a fully active member. The badge is informational only and doesn’t restrict anything the family can do once they sign in.
An import creates the record but doesn’t email anyone, so a family only finds their way in if they use your join link themselves or you send them one. Whenever any imported families haven’t claimed their account yet, the same Import tab shows an Imported families not set up yet card listing them, with a search box and a Select all option so you can send the setup link to one family or all of them at once. A family who signed in but stopped partway through gets a reminder to finish instead of a repeat invitation.
Reviewing applications: Go to Admin › Applications. Use the search bar to find a specific applicant by name or email. Pending applications are listed first; the ones you’ve already acted on sit in a Reviewed section underneath, which has its own status filter (Approved or Rejected). Each row shows the applicant’s answers, any waivers they signed, and their students’ information. Click a row to open the full application. Long answers are collapsible so the review page stays readable. If any of your custom questions has a fixed set of answers (a dropdown, checkboxes), an Answer summary panel next to the queue tallies how the applicants in view answered each one. Click a count to filter the queue to just those applicants. Approve & invite creates their account and sends an invitation email. For someone new to HomeschoolGo, the email’s setup link works once. If they open it after it has expired or been used, they can click Email me a new link on the page they land on, and a fresh one goes to the address on their application, so they don’t need to ask you for another. Reject closes the application without creating an account. They can reapply through the join link if circumstances change. Check the boxes on multiple pending applications (or use Select all) to approve or reject them together from the bulk action bar instead of reviewing one at a time.
If a listed child’s name matches a student already on file under a different family, the application shows a Possible duplicate household warning naming that existing family before you approve. It usually means a spouse or co-parent applied separately instead of using the household invite. Approving still works, but see Household member invites or Merging duplicate families if the two records should really be one.
Changing a member's role
Open a member’s record in Admin › Members and use the Role section to make changes. This is owner-only by default, but an owner can hand it to a specific admin. See Change member roles under Admin permission levels below.
Giving someone access to teach a class
This is usually what you actually want, and it doesn’t touch anyone’s role. Open the class from Admin › Class Catalog, find the Teachers field, and start typing the person’s name or email address to assign them. Someone who hasn’t added a name yet is listed by their email. Any org member can be assigned this way. It grants access to that class’s roster and gradebook in the Teaching section, and their overall role (Family, for example) is unaffected.
Changing someone’s overall role
A member has one role at a time: Family, Teacher, or Admin. Open their record in Admin › Members and use the Change role control to set a new one. Changing someone to Admin gives them access to the admin console immediately. You’ll want to set their permission level at the same time (see below). Changing someone away from Admin revokes that access immediately, but their family data and student records stay intact either way.
Giving someone a title
Every co-op has jobs a role does not describe: nursery coordinator, treasurer, whoever runs hospitality. Open the Member actions menu on their row in Admin › Members, type into Custom role label, and save. It appears beside their name in the member list.
A label is a description and nothing else. It changes nothing about what that person can see or do, and it does not replace their role. Clear the box and save to take it off again.
Transferring Ownership
On Admin › Members, find your own row and open the Owner actions menu (the three-dot icon, which only appears on the owner’s own row), then choose Transfer ownership… Any active member can be the new owner. They don’t need to already be an admin, but they can’t be suspended. After confirming, they become the new owner and you drop to Admin. Only the current owner sees this option.
Admin permission levels
When someone has the Admin role, you can scope their access to specific parts of the app. This lets you delegate work without handing over full control.
Find the admin on Admin › Members, open their Member actions menu, and choose Edit permissions. The available permissions are:
Permissions
Sam Teacher
Manage members
Invite and remove admins and families, and edit the membership application form: its questions, waivers and the default join fee. Suspending a member stays owner-only regardless of this permission.
Change member roles
Change another member’s role between Family, Teacher, and Admin. It’s separate from Manage members and off by default. It doesn’t let an admin change an owner’s role, or their own.
Manage terms
Create, open, close and edit terms, and their schedule, rooms, no-meet days and join fees, plus whether a term is accepting applications. An admin without it can’t open Terms & Schedule.
Manage classes
Create and edit the class catalog.
Manage class enrollment settings
Configure class payment mode, fee exemptions, and the sibling discount. The Class enrollment section of Admin › Settings › Programs. Separate from Manage classes, since it controls money settings rather than the catalog itself.
Manage registration
Add, edit and remove enrollment windows on Admin › Registration, and use Notify families about a term. An admin without it can’t open Registration, and when they copy a term, its enrollment windows aren’t copied.
Manage families
View and edit family and student records.
Delete families
Permanently delete a family and its records. This cannot be undone, so it’s separate from Manage families and off by default. See Permanently deleting a family.
Manage payments
Manage charges, payments, and credits.
Manage subscription
Choose a plan and start or renew the co-op’s HomeschoolGo subscription. Canceling, changing auto-renewal, and opening the Stripe billing portal remain owner-only.
Manage volunteers
Manage volunteer requirements, roles and shifts, and Co-op Jobs. An admin without it can’t open the admin Volunteer or Co-op Jobs pages.
Send announcements
Send announcements to all members.
Manage events
Create and manage events on the calendar.
Manage content
Manage FAQs, links, contacts, documents, custom pages, the business directory, classified categories and the gallery. That covers reviewing member business listings and member photos, and the Business Directory and family gallery upload settings. An admin without it gets the member view of those pages and can’t open Custom Pages or the site importer. Their own business listing waits for review like a member’s, and they upload photos under your family upload setting, the same as a family.
View reports
Access reports and data exports.
Owners always have full access regardless of any permission settings, and the permissions above apply to the Admin role only. Editing another admin’s permissions is always owner-only, even for an admin with Change member roles turned on.
Three permissions sit outside that list. Manage gallery can be granted to a member on any role, including a family or a teacher, so the person who actually takes the photos can run Community › Gallery without being made an admin. Grant it in Admin › Members from that member’s “…” menu, which offers Allow gallery management (and Remove gallery access to take it back). It lets them create albums and upload, caption and delete photos, and nothing else.
Send email blasts works the same way, from the same menu, with Allow email blasts (and Remove email blast access to take it back). Use it for the volunteer who writes your newsletter: they can compose, schedule and send email blasts, and see what the co-op has already sent, without becoming an admin. An Email Blasts page appears in their sidebar, and an Email blasts pill appears next to their name on the Members page. It covers email only. Texting stays with admins, because it spends the SMS credits your co-op has bought.
Create events is the third, granted from the same menu with Allow creating events (and Remove event creation to take it back). Use it for a teacher or parent who plans field trips. A New event button appears on their Calendar, and the events they add go on the calendar for everyone right away, with them as the coordinator, so they see who signs up and can message attendees. Their events are always free and happen on a single date. They can edit or delete only the events they created, and can’t delete one once people have signed up. For a paid or repeating event, or to change someone else’s, they still need an admin. Removing the permission leaves their existing events on the calendar.
Suspending a member
The everyday tool for taking away a member’s access is reversible: Suspend, on a member’s record in Admin › Members (open their Member actions menu and choose Suspend member). A suspended member can still sign in to HomeschoolGo (suspending doesn’t lock their account), but instead of reaching your co-op’s dashboard they land on a page telling them their membership is paused, and they’re hidden from the Families page. Their record, enrollments, and payment history stay intact the whole time. Click Reactivate on the same record at any time to restore them.
Suspend is reversible and keeps everything intact, so it’s the right first move even for a family that’s leaving for good. It keeps their history in your ledger without giving them access. If you need to erase a family’s records entirely rather than just lock them out, see Permanently deleting a family.
Only the owner sees the Suspend option, even for an admin with the Manage members permission. If an admin needs to suspend someone, ask the owner to do it or to transfer ownership to them.
Some entries should go entirely: a test account, or an invite sent to the wrong address. For a member with no household in your co-op, suspend them first. Their Member actions menu then shows Remove from co-op… under Reactivate. Type their name, tick the box to confirm, and their membership is deleted. They drop off the Members list and can no longer reach your co-op. Signing in again on their own doesn’t bring them back. This can’t be undone, though you can invite them again later, and they keep their HomeschoolGo login and any other co-ops they belong to. Someone still assigned to a class has to be taken off it first.
A member who has a household isn’t removed this way, with one exception. Their menu points you to the Families page, where you delete the family instead (see Permanently deleting a family). The exception is a suspended member whose household has another adult with an active login in your co-op, which is what a family merge leaves behind when both records had a login for the same person. For them, Remove from co-op… takes only that login off the household. The household, its other adults, students, and payments stay as they are. If the removed login was the primary contact, the household’s other adult login becomes primary, so check the family’s contact details on the Families page afterward.
Common questions
A teacher wants to also enroll their own children. Do they need two accounts?
No. They can set this up themselves. No admin action needed. Have them open Profile and click the Set up your family card, then add their children. Their family shows up on the Families page automatically and their teacher role is unaffected.
A family applied but I can’t find them in the application queue.
Check whether the application was already acted on. Approved or rejected. Admin › Applications lists pending applications at the top and keeps reviewed ones in a Reviewed section below them. Click that heading to open it if it’s closed, then use its status filter to show only approved or only rejected applications.
I suspended a family by mistake. Can I undo it?
Yes. Suspension is fully reversible. Open their record in Admin › Members and click Reactivate. Nothing was deleted while they were suspended, so their profile, enrollments, and payment history come back exactly as they were.
Can I see which admin made a specific change?
Yes. Go to Admin › Settings and open the Audit log tab (owners only). Every significant admin action is recorded with the person’s name, what they changed, and when.
Can I see every application a family has ever submitted, not just their most recent one?
Yes. Open a family’s row on Admin › Members, open their Member actions menu, and choose View applications. It lists every membership application linked to that family across every term, not just the one that got them approved.