Staffs Management
1–2 days saved for every new joiner
And access is stopped the same minute an employee leaves
In simple words
Staffs Management decides who can log in to the Console and what each person can see and do. This lets you grow your team without giving every new person access to prices, margins, customer data and payment settings.
The problem it solves
Without separate logins and roles, access is all or nothing. Teams start sharing one login, so nobody knows who made a change, and you cannot remove access for one person. New joiners wait for days, and people who have left keep their access for weeks.
What happens without it
| If you do not have Staffs Management | What it means for your business |
|---|---|
| Everyone uses one shared login | You cannot tell who changed a price or a customer record |
| Everyone can see everything | Cost, margin and payment details are open to the whole team |
| Access is set up by IT on request | A new joiner waits 1–2 days before they can work |
| Access is not removed when someone leaves | Ex-employees can still open customer and financial data |
| No way to stop access temporarily | Records are deleted just to block a login, and the history is lost |
| Permissions are given from memory | Access is different for each person, and nobody knows who can do what |
| Invite problems need a support ticket | The new joiner sits idle |
Time you save
Manual way compared with the Console
Typical effort per activity. One working day is counted as 8 hours.
Manual way (spreadsheets, email, phone)With Kitchen365 Console
| Task | The manual way | With Staffs Management | You save |
|---|---|---|---|
| Add a new team member | Raise a ticket, wait for setup, follow up for the invite — 1–2 days | Add the user, select a role, send the invite — 5 min | 1–2 days per joiner |
| Remove access when someone leaves | Follow up with IT — hours or days | Disable access immediately | Risk removed the same minute |
| Change what a team can access | Update each person one by one | Edit the role once, everyone is updated | Hours per change |
| Stop access temporarily | Delete the user and create them again later | Switch access off and keep the record | No rework, and history is kept |
| Resend a login invite | Raise a ticket and wait | Resend it from the staff list | Hours per new joiner |
| Answer an audit question | Collect information from emails | Show the staff list and roles | Hours per audit |
Your process, before and after
✖ Before
Access is given by whoever knows the admin password, and it is not recorded anywhere.
✔ After
Every person has their own login and a role. Adding someone takes minutes, removing them is one switch, and you can show exactly who can do what.
Who uses it
- Admin or operations head — adds people, removes people and manages roles
- Department managers — request the correct role for a new joiner
- Owner — reviews who can see customer and financial data
When to use it
- When a new sales, support or design team member joins
- When someone changes department or responsibility
- When an employee leaves, or access must be stopped for some time
- During periodic access reviews
What each part does for you
| Part of the screen | How it helps you |
|---|---|
| Staff user list | A current list of everyone who can use the Console |
| Add staff user and send invite | New joiners can start work on day one |
| Enable or disable access | Stop access immediately, without losing the record |
| Resend invite | Solves the most common joining problem |
| Roles and permission tree | Each person gets only the access their job needs |
| Edit role | One change updates everyone with that role |
Step-by-step guide
See Staffs Management.