Home/Modules/People/Users & Permissions
🛡
People · Role-based

Users & Permissions, every action accountable

Schoolyam Users & Permissions controls exactly who can do what: role-based logins with menu-level rights, separate approval rights for sensitive actions like concessions and receipt changes, a second transaction password for money-touching screens, and logs that record every user’s actions.

Menu-levelrights per role
2ndtransaction password
Loggedevery user action
Scopedcoordinators see their classes only
Everything inside

What’s inside Users & Permissions?

Every card below is a working feature in the live product — not a roadmap item.

👥
Roles & usersPrincipal, accountant, front desk, coordinator, teacher — each a role with its own menus.
📋
Menu-level rightsRights are per screen — the fee clerk sees fees, not payroll; and vice versa.
🛡
Sensitive-action gatesConcession approval, receipt modification, backdating — separate explicit rights.
🔑
Transaction passwordA second password guards money-touching actions — login alone isn’t enough.
🎓
Class-scoped accessCoordinators and teachers see their own classes and students — not the whole school.
📊
User action logsMenu-wise usage logs per user — who did what, when, from where.
🔁
Password managementForced resets, admin-assisted changes and password policies from one screen.
Clean handoversStaff leaves? Deactivate the login, reassign the role — access ends the same hour.
Point by point

Key features of Users & Permissions

Scan any group in seconds — every point is a working capability, not a promise.

Role-based access

  • Menu-level rightsEach role sees exactly its screens.
  • Class-scoped viewsCoordinators see their classes only.
  • Day-one productivityNew staff get a role, not a tour.

Money gates

  • Explicit sensitive rightsConcessions, corrections, backdating.
  • Transaction passwordLogin alone can't move money.
  • Approval workflowsSecond eyes on discounts.

Accountability

  • Action logsWho did what, when, from where.
  • Instant deactivationAccess ends the hour someone leaves.
  • Password managementResets and policies from one screen.
Automation

How does it run itself?

1
Roles mirror your org chartDefine roles once; new staff get a login by role and see exactly their screens on day one.
2
Sensitive actions need explicit keysMoney and marks screens check specific rights and the transaction password — job titles don’t grant them, you do.
3
Logs answer every questionWhen something looks off, the action log shows the who/what/when in minutes — accountability without accusation.
Proof, not promises

Which screens do you actually get?

Real screen names from the live Schoolyam dashboard — ask for any of them in your demo.

Add UserAdd User RoleAdd User MenuUser Menu Log ReportManage PasswordChange Transaction PasswordUser List

Role-based · priced module-wise — pay only if your school uses it · add anytime

Questions principals ask

Frequently asked

Can we stop the fee clerk from seeing payroll (and vice versa)?

Yes — rights are menu-level per role. Each login sees only its assigned screens; there is no “view everything” default. Sensitive actions inside a screen carry their own additional rights.

What is the transaction password?

A second password, separate from login, required for money-touching actions like receipt modification or backdated entries — so a borrowed login can’t move money.

If something looks wrong in the books, can we find out who did it?

Yes — user action logs record every screen use and change with user, date and time. Most “mysteries” resolve in one report.

Works together with

See Users & Permissions live on your school’s data.

A 30-minute demo with your classes, your fee structure, your report-card format. Free, and on your screen — not a slideshow.