Give every student and resident the right access, without the daily admin burden.
Campus and hostel networks serve people with different access rights, devices and schedules. BryanNet brings those accounts and access rules together in one place.
A controlled network for students, residents, staff and visitors.
What makes access difficult?
Shared credentials are difficult to control
A common password can travel beyond the intended users, while changing it disrupts everyone.
Manual enrolment does not scale
Creating accounts one by one for a new intake is slow and easy to get wrong.
Access outlives eligibility
Students, residents and visitors can retain access unless someone remembers to revoke it.
The BryanNet approach
Individual accounts and controlled access
Give users their own router accounts and manage active subscriptions and permitted concurrent devices centrally.
Import and provision users in batches
Prepare student or resident records in CSV files, create accounts in bulk and assign the appropriate access entitlement.
Access with a defined lifecycle
Use plan validity, subscription expiration and administrative suspension to control when access starts and stops.
How it works
Bring users into the system
Import approved students and residents or create accounts individually.
Assign their access
Apply the relevant plan or entitlement and provision router accounts.
Manage the term or stay
Review subscriptions and devices, and expire or revoke access when the entitlement ends.
Relevant capabilities
CSV account imports and batch provisioning
Plan and subscription assignment
User-specific router credentials
Concurrent-device controls
Customer account and device visibility
Operational and subscription reporting
Institutional identity-system integrations and automatic student-status synchronization require a separately agreed integration scope.
Discuss this solutionCommon questions
How can universities and hostels manage student or resident access?
Create or import student and resident accounts, assign the appropriate access entitlement, and manage validity, subscriptions and permitted concurrent devices. Access can expire or be revoked when eligibility ends.
Institutional identity integration and automatic student-status synchronisation require a separately agreed integration scope. Available features depend on the edition.