System settings

Purpose: show where long-lived configuration lives: branding, sharing, integrations, and defaults. Exact labels follow the live app; this page stays conceptual so it does not go stale on every small UI tweak.

Who can use this

Administrators with access to Settings, Admin, or Organization areas. Other roles may see a read-only subset or nothing.

Steps

1. From the dashboard, open Settings (or Admin → Settings).
2. Review Facility or Organization blocks: time zone, display name, default locations, and module toggles.
3. Open Sharing (or District / peer settings) to control which other schools can view or request loans from your inventory.
4. Save after each logical group of changes. If the app shows a success message, the new rules apply on the next page load for most users.
5. Communicate big changes in email or staff meeting—people notice when browse or loan rules change.

Screenshot: the sharing screen with “view” vs. “request loan” checkboxes—high value for districts.

Expected result

The behavior you see in testing matches what teachers experience: shared browse, loan requests, or restrictions line up with policy.

What happens next

• User management to give people roles that match the new settings.
• Troubleshooting: permissions errors if someone still cannot access a feature.

Common problems

• Two admins change the same setting — last save wins; maintain one owner for production-wide flags.
• “Works in staging, not in production” — confirm you saved in the right environment; ask your technical contact if you use more than one deployment.

Related

• Permissions