Bus Request Approver and Admin User Guide

This guide explains the daily approver workflow and the administrator controls for access, rates, vehicles, districts, settings, and notifications.

Approver sign in and access

  • Open the Transportation staff area and sign in with your SBCSS Microsoft Entra account. Complete multifactor authentication when prompted.
  • A successful Entra login must match an active local user with an assigned role. The Tech Services Web App Team determines whether Object ID matching is also required.
  • If access is denied, ask an administrator to verify your email address, Active setting, and role. Tech Services can verify the configured Object ID requirement.

Approver workflow

  • Find the request by confirmation number, requester, email, district, or status.
  • Open the confirmation and review the full trip, passenger requirements, itinerary, options, vehicle pricing snapshot, and history.
  • Choose the correct status and add a concise note when context will help the requester or another approver.
  • Select Update status. The system records the change and queues workflow notifications.

Status meanings

StatusUse it when
PendingTransportation review or a decision is still required.
ConfirmedTransportation has approved and confirmed the request.
DeniedTransportation cannot approve the request.
CancelledThe trip is no longer proceeding.
DeletedThe request should be treated as removed while retaining its audit history.

Administrator capabilities

  • Users: authorize staff, assign roles, manage notification preferences, and deactivate access.
  • Rates and vehicles: create effective-dated rates, set the initial block, and maintain vehicle counts and passenger limits.
  • Districts: add, order, activate, or deactivate the choices shown on new requests.
  • Settings: maintain application labels, contacts, advance notice, maximum trip date, and after-hours information.
  • Notifications: review delivery history and retry failures after correcting the underlying problem.

Configurable Entra Object ID matching

  • The Tech Services Web App Team controls the Object ID requirement through server configuration.
  • When enabled, the Entra tenant, Object ID, and email address must match the active local user.
  • When disabled, the verified tenant and email address must match. The Users-page Object ID field becomes read-only and may be null.
  • Existing Object IDs remain stored while matching is disabled. Administrators continue to manage users and roles but cannot change this server setting.

Administrator operating guidance

  • Assign the least role needed and deactivate access instead of deleting historical identity records.
  • Prepare future rate periods before their effective dates and verify every amount and block length.
  • Confirm passenger limits and vehicle availability after fleet or contract changes.
  • Retry notifications only after resolving the delivery problem.

Getting help

  • Use the contextual Help link on the current application page for instructions specific to that page.
  • Contact Transportation for request or operating questions and use the website support contact for access or technical problems.
  • Include the confirmation number and a short description of the problem. Never send passwords, client secrets, or unnecessary requester information.