For everyone
What is Kimchi?
The lay of the land, five minutes before you set anything up.
Kimchi is one system for how your restaurant group runs: the knowledge, the training, the daily checks and the guest feedback, connected instead of spread over binders, group chats and spreadsheets.
The building blocks
Three concepts carry everything else. Set them up once, and every module uses them.
| Concept | What it is |
|---|---|
| Workspace | Your company's own Kimchi. Its name, logo and language live in Settings. |
| Locations | Your sites. Content and checklists are assigned per location, so people see what applies where they work. |
| Groups | Roles you define, like Chef or Front of house. A group decides what its members can do, and it is how you assign training and work to many people at once. |
The modules
- Knowledge & SOPs: your standards and procedures, written once, shared with the people who need them.
- Training: courses built from the documents you already have, assigned to groups or individuals, with progress you can see.
- Checklists: the daily, weekly and monthly checks each location runs.
- Guest feedback: reviews come in, Kimchi reads them, and recurring problems become opportunities with an owner.
- Projects: the bigger, one-off work: openings, renovations, seasonal menus.
- Ask Kimchi: the assistant in the top right of most screens. Ask it anything about your team, your content or the page you are on.
Who sees what
Kimchi looks different depending on who is signed in. Admins and managers see the whole workspace: every module, every location, every person. Staff see their own day: the training assigned to them, the checklists for where they work, and the knowledge shared with their group. You decide those boundaries in one place: groups and permissions.