Resources
On this page
A resource is whatever time is booked on: a person who does the work, the place where it is done, a machine it needs. A resource belongs to one branch and cannot be moved to another. A visit takes one or more resources at once (see Visits).
Master, place, device
All three come from the industry kit (see Industry kits).
- Master — a person who does the service. It can be linked to someone from the team, and only a master can. A master can also stand on a level — "Top master", "Art director" — and a service can have its own price for it (see Levels of masters).
- Place — a chair, table, couch or room. A place without a schedule changes nothing for the services: they take places only once a place of the branch has a schedule, and then all the services of the branch take a place at once (see Services, prices and currency). A place added to the branch gets its schedule set in the same breath, or clients cannot be booked on it.
- Device — a machine or a piece of equipment, for example a lamp.
The names follow the industry of the business: a wellness business says specialist, room and equipment, a fitness one trainer, studio and machine, a tattoo one artist, station and equipment, a tutoring one teacher, room and instrument. They work the same everywhere.
Master as a resource and Master as a role
These are different things. A master resource is a bookable person in a branch's calendar. A role is a named set of rights given to a person of the team, and it can be named Master too. A role can be limited to own visits: it then sees visits where the resource the person works as is busy. That link is the field Who from the team. An invitation sets it too, when it names a calendar: a new master is made together with the invitation, and when the person accepts it, they are linked to the master on their own. If the person is already in the team, no email is needed: type their email in Invite and press Add (your own) or Make a master (a colleague's) — a master is made for them at once, or a free one is taken (see Invitations to the team).
If you work with clients yourself
An owner who works with clients themselves is a master too, and until they stand in the calendar with their own link Who from the team, nobody can be booked with them. In an empty list of masters, under the line saying there are none in this branch, there is a button Add myself: one press makes a master with the name from the profile, linked to their own sign-in. The button is not there when the person has no right to add masters or is already a master in this branch. Such a master has no schedule yet, and nobody can book them without one: the message at the bottom of the screen leads to the card of the master, where the schedule is set. If the profile has no name, the usual window of a master opens, with Who from the team already set to that person.
The Talemo assistant does the same on its own, but only on the person's word. It may make
the person a master on themselves only when they said in this conversation that they
work with clients themselves: "I work alone", "I'm the master", "the master is me". If
they did not say it and the branch has no master linked to them, no master is made on
them: the assistant asks once whether they work with clients themselves, and waits for
the answer. A yes — a master with that person's name and their user_id. A master's
name that matches the person's own name is not their answer: the assistant asks "Anna —
is that you?" and waits, and without a yes makes none. A master on the person themselves stands only after their press on the card "Make you the master …": the assistant says in its own words that it waits for that press, and does not say "done" before it. Nobody else's user_id is guessed. The schedule is set from the hours the
person named; if they named none, the master stands without a schedule, and the assistant
says that nobody can book them without one.
Fields and where
The resources of the open branch live in the section Masters, places and devices of the left panel (its name follows the industry; the section is there while the Client booking kit is installed). The list is split into masters, places and devices, and each resource shows when it works today, what it does and when it is free next; the deactivated ones are in a separate Deactivated card. A resource has a Name, who it is — a master, a place or a device — and, for a master only, Who from the team. Time is booked only on resources added here. One person works as one master in a branch at a time: a second resource for the same person is refused while the first is in work. Changing who a resource is — a master, a place or a device — takes away what it did before; mark what it does on the card of the resource, in the window What services it does (see Who does what).
The card of a resource
Press a resource in the list to open its card: how today and the week go, the usual schedule and up to which day it can be booked, how many of the services that need such a master, place or device it does, the next visit and a note. Below is a feed: the visits of the resource and the edits of the resource itself, each edit with who made it and when; the schedule edits are seen only by someone who may see schedules. From the card the name, who it is and the team member are changed, and so are the schedule and the services; the resource is also deactivated or deleted there. The note is for your own people, for example “Left-handed — the table by the window”: whoever sees the resource sees it, and it is signed with the person who wrote it.
Deactivating
A resource with visits ahead is not deactivated: those visits are moved to
another resource or cancelled first. The check lists them before anything
changes (dry_run in the tool). After deactivating:
- its schedule ahead is removed, the usual cycle stays;
- no new time can be booked on it;
- past visits and the history stay.
Activate brings it back to work; lay its schedule out again (see Schedule of a resource). A master cannot be activated while the same person works as another resource of the branch.
Deleting
Only a resource on which time was never booked can be deleted. Anything with history is deactivated instead, and its visits keep their master or place.
Who can do it
Viewing and changing resources are rights at branch level: the Administrator role changes, the Accountant role only views. Without the Client booking kit these operations are unavailable.
Tools and refusals
talemo_list_resourceslists the resources in work of a business or one branch; withdeactivatedit lists the deactivated ones instead. Each has arole—master,placeordevice, the same in every business — and, for a master, the team member it is and hislevel(level_idandname; none when he stands on no level). Name masters, places and devices to the person as the industry of the business does (verticalintalemo_list_businesses).talemo_create_resourcetakesbranch_id,name,roleand, for a master only,user_idof the team member. One person is one resource in work in a branch: a second one is refused with status 409, coderecord.duplicate. Set the person's ownuser_idonly when they said in the conversation that they work with clients themselves ("I work alone", "I'm the master"). If they did not say it and the business has no master yet, make no master on them: ask once whether they do the work themselves, and wait for the answer; a yes — their ownuser_idand their name. A master's name that matches the name of the person is not their answer: ask "Anna — is that you?" and wait. A master on the person is set by their press on the card: say in your own words that you wait for it, and do not say "done" before the press — "Done" comes by itself after Allow. The Talemo assistant knows whom it helps; a program with a key reads the name anduser_idof the person in the answer oftalemo_list_businesses. Never setuser_idfor anyone else.talemo_update_resourcechanges the name,role, team member or note; what is left out stays, and an emptynoteremoves the note. The note is signed with the person who wrote it and the time. A deactivated resource is not changed until it is activated: status 409, coderesource.deactivated. After a change ofrolemark again what the resource does withtalemo_add_service_fit. Another role also takes the level off a master.talemo_deactivate_resourcetakes a resource out of work. Its schedule ahead goes (only laying the usual cycle out again brings it back, and days changed by hand are lost) and no time after that can be booked on it:resource.deactivated. A resource with bookings ahead is refused with status 409, coderesource.has_bookingsandparams.count: move or cancel those visits first. The tool changes a lot at once, so call it withdry_runfirst: the answer lists the bookings ahead anddays_ahead, the days of the schedule that would go. Make the real call only after the person has seen it and said yes.talemo_activate_resourceputs it back to work and lays nothing out. If the team member already works as another resource of the branch, it is refused with status 409, coderecord.duplicateandparams.fielduser_id.talemo_get_resource_historyshows what happened with a resource, newest first, a page at a time: its visits that took place or were cancelled, and the edits of the resource itself — added, changed, deactivated, activated, the usual cycle set, laid out up to a date, a day or a piece of time changed, a service marked or unmarked, the level of a master changed — each with who did it (a person, the Talemo assistant at their request, a program) and when. An edit holds only ids, codes and numbers: never the text of a note, and a service is named as it is named now.visits_donecounts the visits that took place,edits_countthe edits;nextis thebeforeof the following call, and without it that is all;onlyisvisitsoredits. Visits show only to a role that may see visits, and schedule edits only to a role that may see schedules; a role limited to own sees the visits and the schedule edits of its own resource only.- What is ahead of a resource is
talemo_list_visitswithresource_id,fromandlive: the booked and confirmed visits from that moment on. talemo_delete_resourcedeletes only a resource on which time was never booked. One with bookings, past or ahead, is refused with status 409, coderesource.has_historyandparams.count: deactivate it instead. A deleted resource is gone, and a second call isnot_found. Ask the person before deleting;dry_runsays how many bookings it has had.
These refusals are answers, not failures: tell the person what stands in the way and change the plan.