Sorting meetings by project or topic, and the one thing a label never changes.
A label says what a meeting is about: a project, a client, a topic. A meeting can wear any number of them, and every label opens the meetings that wear it, across every workspace. Labels come with Chui's paid plan; on the free plan, reaching labels offers the paid plan instead, in the same place.
A label never changes who reads a meeting. That is the workspaces' job alone. Under a label each person sees only the meetings they could already open: a meeting in somebody's own «Private» workspace that wears the team's label is still read by its recorder alone — the team's admins included.
In a team, labels belong to the whole team: anybody in it makes them, and everybody sees and uses them, across every workspace. Alone on the paid plan, they are your own. Only the person who made a label — or an admin of the team — can change or delete it.
Every label has a name, a colour and a short description: one or two sentences saying what it is for and who the meetings are with. The app asks for the description because Chui reads it to decide which meetings are about the label. A label made without one (by typing to an assistant) still works by hand, and Settings › Labels marks it so a description can be added.
Only the person who recorded a meeting can put labels on it or take them off; colleagues who read it see its labels.
When Chui writes a meeting's summary, it puts on the labels the meeting is about — only labels that already exist, judged by each label's description, so a label without a description is never put on by Chui. Its pill says «added by Chui»; one tap on the × (or unticking it in the sheet) takes it off for good — summarising the meeting again does not put it back.
One switch turns this off: Settings › Labels › «Chui labels meetings itself», on by default. In a team it is one switch for the whole team.
Chui never makes a label by itself — a label is shared with the whole team. It proposes them:
Settings › Labels lists every label with its description, how many meetings wear it and who made it, and is where a label is changed or deleted. Deleting one asks first, takes it off every meeting, and deletes no meeting.
An assistant connected to Chui does all of it: list_labels() shows them, create_label() makes one (ask for the description), update_label() changes a name, description or colour, add_label_to_meeting() and remove_label_from_meeting() put one on a meeting and take it off, and list_meetings() with a label lists the meetings under it. Deleting asks first: prepare_delete_label() says how many meetings would lose it, then delete_label() with its token. list_label_proposals() shows what Chui proposes, answer_label_proposal() saves or declines it, and set_automatic_labels() turns Chui's own labelling on or off.
On Chui Pro, update_label() can also teach a label a summary shape of your own, which every meeting wearing it then follows (since build 230); What happens after you stop says how.