Which accounts can open your Chui, which devices are signed in, and how to end one.
Two different lists, and the difference matters when something has gone wrong.
A way of signing in is the proof of who you are — an Apple, Google or Microsoft account. It survives every sign-out, so somebody whose Google account was taken needs this list; signing devices out leaves that door standing.
A device is something signed in right now. Signing it out ends that session and changes nothing about who you are.
list_sign_in_methods() gives every one on the account, the address each is under, and when it was last used. remove_sign_in_method() takes one away.
Chui refuses to remove the last one, so nobody can lock themselves out of their own account. Nothing on the account is touched by a removal: not a meeting, not a person, not a setting.
Adding one cannot be done from an assistant. It is done in the Chui app, under Settings → Ways to sign in — see Chui inside an assistant for why a connected assistant is allowed to change everything on an account and never to make a second key to it.
list_devices() gives every phone, Mac, browser and assistant currently signed in, newest use first, with the one you are talking through marked. A connected assistant is an ordinary session and appears there beside the phones.
sign_out_device() ends one of them. sign_out_other_devices() ends all of them at once except the one asking — the thing to reach for when a phone is lost.
No meeting is deleted. The recordings a device made stay exactly where they are, with their titles, transcripts and summaries, and whoever holds it can sign in again with any of the ways above. What a sign-out does is end that device's reach now: it can read nothing further and is sent no more notifications.
One thing does go, and only when the last session goes. An account nobody is signed in to has no business holding a live Google or Microsoft grant, so signing out the very last device also lets go of a connected calendar — and clears the link each past recording had to the calendar entry it was. The meetings keep their names, their guest lists and everything said in them; what is lost is «which diary entry was this», which is what «what did we say last time» follows. Reconnecting the calendar later is a fresh connection and does not bring those links back. Signing out one device out of several never does this.
If the connection you are talking through is the one signed out, that is the end of the conversation with Chui — nothing else can be asked after it.
An API key lets a server — a meeting service, a script — send meetings into this account by itself. Only the account's owner makes one, and on a company account only its admins; the key is shown once, when it is made, and nobody else sees or ends one.
list_api_keys() gives every key with its name, who made it and when a server last used it. prepare_revoke_api_key() then revoke_api_key() end one, in two steps: it stops working at once, and the meetings it already sent stay where they are.
create_api_key() makes nothing. An assistant cannot make a key, because a key goes on working after the assistant is signed out; it answers with where to press Make a key in Chui — Settings → API keys.