Public Tutorial

Library Operator Tutorial

Public onboarding guide for owner/admin/staff. No login required.

First login and branch selection

  1. Sign in from /login and complete authentication.
  2. If multiple branches are listed, select the correct working branch before data entry.
  3. Confirm selected branch from the top selector before attendance or fee work.
  4. If branch is wrong, switch first and only then create/update records.

Day-1 setup order (must follow)

  1. 1

    /institution-profile

    Configure institution profile (legacy alias: /library-profile).

  2. 2

    /students

    Create core student records with clean roll and student codes.

  3. 3

    /seats

    Create seat inventory using real physical seat labels.

  4. 4

    /attendance

    Run first end-to-end check-in/check-out verification.

After these 4 steps, continue optional setup in /shifts, /lockers, and /fee-structure.

Module-wise usage highlights

/institution-profile

Keep institution name, contact, address, and geofence location accurate.

/students

Keep attendance-enabled students in Active status and test bulk upload with sample rows.

/attendance

Use roll/student code for check-in/out and close open sessions by day end.

/fee-structure + /fees-collections + /orders

Set fee structure first, record manual collections, and track online payment orders.

/seats + /lockers

Keep one active seat assignment per student and release lockers on exit.

/reports + /audit-trail

Use reports for daily/weekly review and audit trail for issue traceability.

/notifications

Send concise announcements only after validating audience and timing.

/staff + /settings + /support

Maintain least-privilege staff access, keep support contacts updated, and raise tickets with evidence.

Module visibility troubleshooting

  1. Plan check: open /plans and verify the module is included in your active subscription.
  2. Role check: some modules (for example /orders navigation) are owner/admin only.
  3. Permission check: staff module permissions must be enabled by admin.
  4. Branch check: confirm correct branch context before reporting missing data.
  5. Still blocked: ask owner/admin or raise a ticket from /support with screenshot + timestamp.

Daily checklist

  • Confirm branch selection before operations start.
  • Review /dashboard snapshot for occupancy and dues.
  • Complete check-in/check-out flow in /attendance.
  • Reconcile manual collections in /fees-collections.
  • Check unread alerts in /notifications.

Weekly checklist

  • Review attendance and payment trends in /reports.
  • Validate seat and locker allocations in /seats and /lockers.
  • Verify defaults and support contacts in /settings.
  • Close pending issues in /support.
  • Audit staff access in /staff.

Need in-app help too?

Use /guide for operator-facing help after sign-in, or raise a support ticket from /support.