What Slota is

Slota is staff scheduling and attendance for shift-based teams. One organisation, many locations, one roster.

The pieces

• Schedule — who works when. Managers build it as drafts, then publish; publishing is what makes shifts visible to staff and sends the notifications.
• Deployment — who stands *where* on a given day. It sits on top of an already-scheduled day and never creates hours of its own.
• Time clock — what actually happened. Clock-ins from a kiosk or mobile become timesheet entries, which become payroll numbers.
• Time off & availability — the constraints. Availability is a standing weekly pattern; time off is a dated request that needs approval.
• Tasks & onboarding — what people must read, do or sign, including PDF documents signed on a phone.
• Messages & newsfeed — direct messages, group chats, and organisation-wide announcements with read tracking.
• Reports — labour, payroll, attendance, feedback, time off and sales analytics over any week.

Two ways in

• Web — the full product, including everything managers and administrators need.
• Android app — the employee experience (and a manager subset), built for people who do not sit at a desk.

Both use the same account and the same data. A change on one appears on the other.

Three roles

Everything you can see and do comes from your role — Employee, Manager or Admin. See *Roles and what they can do* for the full matrix.

Slota enforces roles on the server for every request. Hiding a button is never the only protection.