The right work, for the right person.
Access is built around responsibilities, not a shared login. A person is assigned a role at a location, sees the dashboard their job needs, and can only take the actions that role is meant to take.
Two worlds, one boundary.
The organization that operates HostedERP runs the shared environment. Each business runs its own environment. The boundary between them is structural: the platform operator administers addresses, subscription status and platform-wide defaults, not a business's operational data.
Inside a business, roles decide what a person can see and do. A role is assigned at a location and activity, so a team member can be a Manager at one branch and a Team Leader at another without a second account.
- Ten staff roles, from administrator to concierge
- Assignments scoped to a location and business activity
- One person, more than one role — one identity
- Guests and customers are not system users
What each role is responsible for.
The profile is the authority. The table below is a quick reference once the profiles are understood.
Administrator
Owner-levelFull business administration: staffing, security posture, branding, locations and configuration. Reports to ownership; supervises managers and, jointly, the support team.
Support team
InternalInternal troubleshooting and escalation, with access that mirrors the administrator. Reports to ownership jointly with the administrator.
Manager
Cross-departmentOversight of daily performance, reporting, spend approval and the decisions that follow a flagged variance — from the desk, the floor or a phone. Reports to the administrator.
Team leader
ShiftSupervises the shift, manages live orders and supports the team on the floor. Reports to the manager or administrator.
Waiter
ServiceFront-line order taking and service: tables, orders, serving status and payment. Reports to the team leader or manager.
Receptionist
Front deskReservations, check-in and checkout, key-card issuance and return, and the guest's billing record. Reports to the manager or hotel governance.
Hotel governance
HospitalitySenior on-site oversight of the property's hospitality operation. Reports to the manager; supervises reception and concierge.
Hotel concierge
Guest servicesGuest services and requests, supporting the stay without access to financial administration. Reports to governance or the manager.
Inventory officer
StockWarehouse and department stock: receiving, dispatch, usage, counts and the movement history. Reports to the manager.
Financial officer
FinanceReconciliation, payments, purchasing approval and period close. Reports to the manager or administrator.
Important actions have a path, not just a permission.
Roles are not only about what a screen shows. They shape how work moves between people, so a consequential action is reviewed by someone equipped to review it.
A department needs stock
The manager raises a request. The inventory officer checks it against what the warehouse actually holds at that moment.
Supply is insufficient
A purchase order is raised and moves to the financial officer for processing and validation before dispatch.
A bill is disputed
The receptionist can review the booking and billing history, but a genuine adjustment is escalated to a manager or financial officer.
An account is locked
The administrator or support team reviews the login history and unlocks it. A manager cannot bypass account security.
A completed order must change
Reopening a closed order is restricted to trusted roles because it changes figures already counted in a shift.
The quantity is checked when the inventory officer confirms it. An unconfirmed request is a note of intent, not a hold.
Layered protection at the point of login.
Security is not a single password prompt. It is a sequence of controls that match the sensitivity of the work and the device in use.
Progressive lockout
Repeated failed attempts trigger a temporary lock. The remaining attempts and lock duration are visible, and an administrator or support team member can review the login history.
Biometric & security keys
Where the device and policy allow it, staff can verify with a fingerprint, face recognition or a hardware security key instead of typing a password again.
Step-up re-authentication
A session can require identity re-verification after inactivity or a device unlock, so a shared terminal does not stay open to the next person who walks past.
Security alerts stay on
Suspicious login and security notifications cannot be muted by an individual. They remain part of the record regardless of personal notification preferences.
Shift boundaries
Shifts attribute activity to a team and a window of time. The team list becomes final once the shift closes, preserving accountability.
Business isolation
Even a platform-wide mistake cannot expose one business's operational data to another, because the records live in separate databases.
One person, more than one role.
An experienced team member can be a Team Leader at the flagship and a Manager at a newer branch, using one account. Role assignments follow the location, so the platform reflects the real organization rather than forcing duplicate identities.
Model your roles before you roll out.
We will map who does what at each location, which approvals should be separated, and where a single account with two assignments is the cleaner answer.