In this guide
Keep authorized billing access, academic-information permission and ordinary family coordination separate.
Start with the action, not the relationship
A parent, guardian, sponsor or trusted helper may have a legitimate reason to assist with a university task. That relationship does not explain which information they need or which access the university has authorized. Begin with the action: viewing a bill, paying a charge, discussing an academic record, or helping organize dates. Each has a different information boundary.
BC’s current billing page describes My Bill and student-authorized third-party payer access. A separate Student Services notice from August 2019 describes proxy access for course and grade information. The age and separate purpose of that notice matter: this article does not treat its old interface directions as a verified current procedure.
Separate three kinds of help
Administrative assistance might mean reminding someone to check a due date. Access assistance means using an explicitly authorized role to view or act in a system. Advice might mean discussing a decision after the student chooses what to share. These activities are not equivalent and need not all be granted to the same person.
Write the intended task in one sentence before setting anything up: “This person needs to see billing statements and help with payment.” Then check the official access route for that purpose. Do not substitute the student’s main credentials for a purpose-specific route, and do not assume a billing role includes academic information.
A fictional family handoff
Imagine a student and a relative agree that the relative will help manage billing reminders. The relative asks for the student’s password because it seems quicker. That shortcut would expose unrelated services and make it harder to distinguish who performed an action.
A more careful conversation separates the tasks. The student checks the current official instructions for authorized billing access; the relative uses their own authorized route if established. They agree who checks new statements and how they will confirm an intended action. This example does not create access, authorize a payment or establish what any actual account allows.
Permission should have a clear boundary
Before granting access, read what the official role permits, how it is managed and how to remove it if circumstances change. Ask the relevant office if the scope is unclear. A familiar role name is not enough evidence to infer every feature or data field visible to that person.
Keep family coordination separate from the credentials themselves. A shared note can record that a statement needs review without containing a password, a bank account or a copy of the full student record. When an actual financial action is needed, verify the amount, destination and account through the appropriate official process.
Do not confuse notification with completion
A reminder email, a role invitation and an account transaction are different events. Decide which evidence shows the agreed task is complete and who will check it. Otherwise each person can reasonably assume the other has handled the final step.
For academic-information access, consult current BC instructions rather than relying on this article or the historical proxy notice. For questions about privacy rights and permissions, seek the relevant institutional guidance; this article is not legal advice. Campus Taskbook cannot inspect permissions, create a payer role, recover a password or determine an individual’s disclosure rights.
Read next: Read the bill, award, and payment timeline separately, or When a university message pressures you to act.