Add and read team handbook guides
Where the team reads its handbook, and how to add, change, reorder or remove a guide.
The Team handbook (staff only) in the editor's list is a set of guides for the Guesthaus team: how to run the staff dashboard day to day, look after creators and producers, run events and get people signed in. It is not part of the website. This help centre teaches the editor; the handbook teaches the staff dashboard and the people side of the business.
Where the team reads it
- On the staff dashboard, the Site copy card has a link, Open the team handbook. It opens the guides inside the editor.
- Only people who can sign in to the editor can open it. There is no public address, nothing on the site links to it, and search engines never see it.
- Because the guides are read inside the editor, a saved change is there straight away for the next person who opens it. Nothing needs to publish.
Add a guide
- Open Team handbook (staff only) in the list on the left.
- Choose Add File.
- Fill in:
- Title: what the guide helps with, for example "Approve and look after creators". The guide's file name is made from the title when you first save it.
- Position in the list: guides are listed from the lowest number to the highest. Look at the numbers the other guides use (they go up in tens: 10, 20, 30 and so on) and choose one in a gap, for example 45 to go between 40 and 50. Give every guide its own number.
- Summary: one sentence saying what the guide is for.
- Guide: the steps. Numbered lists work well for anything done in order.
- Choose Save.
Change, reorder or remove a guide
- Change: open the guide, edit it and save.
- Reorder: change its Position in the list and save.
- Remove: open the ⋯ menu on its row in the list and choose Delete. If another guide tells people to read it, update that guide too.
Never put these in a guide
Everyone who can sign in to the editor can read every guide, and every saved version is kept in the site's content history, so deleting the words later does not remove them. Never write these (the site also refuses some of them):
- passwords, sign-in codes, sign-in links or keys of any kind
- a creator's, producer's or guest's private details, such as their email, phone number or private notes
- how the site's hosting and servers work; that stays with the Guesthaus engineering team
If a job needs one of these, say where to get it ("ask the Guesthaus team for the sign-in") instead of writing it down. If you find one in a guide, delete it, save, and tell us (see Who to contact) so we can change it.