Role-based access
Students, lecturers, staff reviewers, and administrators use role-appropriate views so each user sees the workflow information needed for their role.
Security overview
Practical safeguards for timesheet workflows.
This public overview summarises the controls Pay Me Bro uses to support account access, school-level workflow visibility, and responsible data handling.
Core controls
Security starts with simple boundaries.
Pay Me Bro keeps user roles, school records, support channels, and payment boundaries explicit so schools can operate the workflow with confidence.
Account setup
Staff accounts are loaded through an onboarding process and users receive setup instructions through controlled school launch communication.
Audit-friendly records
The workflow is designed to make submission, approval, rejection, export, and processing status easier for schools to review.
Data handling
Use only what the workflow needs.
Pay Me Bro is intended to process timesheet workflow information, user profile details, school configuration, and related records needed to support the service.
School responsibilities
- Provide accurate staff and school setup information.
- Tell users which rules and deadlines apply.
- Keep payment decisions and payroll processing inside the school or university process.
Pay Me Bro responsibilities
- Support the platform workflow and onboarding process.
- Maintain clear account, support, and escalation routes.
- Keep platform boundaries clear in user-facing communication.
Public summary only
This page is a public, plain-language overview. Detailed security architecture, credentials, internal support procedures, and private contracts are not published on this site.
Payment boundary
Pay Me Bro does not run payroll, move money, or guarantee that a student has been paid. Payment remains part of the university or school process.