Referral tracking with consent and attribution kept visible.

Record a referral claim

An authorized agent user can submit a referral against their agency organization. The platform records attribution history and can flag possible competing claims for Admin review rather than silently transferring ownership.

• Multiple claims can be reviewed where they conflict.
• Approval and revocation are recorded as distinct events.
• A claim alone does not authorize broad access to a student's profile.

Student consent controls access

Explicit student consent is required for agent access, including where the agent originally introduced the student. Consent is bounded, can be withdrawn and does not automatically expose every field or document.

• Mediated contact is the default rather than unrestricted contact details.
• Document sharing is scoped to selected versions where granted.
• Access should stop when the relationship or consent is no longer active.

Follow permitted application progress

The agent view is intended to show only the referral-linked information permitted by the active relationship and applicable access policy. The agent does not submit applications, decide university outcomes or update student-owned data unless a specific workflow permits it.

Understand commission separately

Referral attribution is separate from a commission contract and per-application entitlement. A referral or conversion does not itself mean a commission has been earned, approved, invoiced or received. Financial records are not exposed to students.

Organization boundaries matter

Agency staff need an active membership in an approved agency organization. Requests are checked server-side and scoped to that organization; client-supplied student or organization identifiers cannot grant access.