The default profile is the one telekit auth set-token uses. telekit send without --profile uses this chat’s bot on a bridged turn, then ~/.telekit/send-profile outside a turn, else default. 
telekit profile list
telekit profile add alerts
telekit profile set-token alerts
telekit profile enable alerts
telekit profile disable alerts
telekit profile status alerts
telekit profile rm alerts --delete-token --yes
Each profile has its own token (stored in the Keychain), its own poll state, and its own grants. Each profile also has its own group allow list. Privacy mode is per bot in BotFather. See Group chats. One daemon can long-poll tens of bots (one bot per working folder, plus an optional alerts bot). Heartbeats still use telekit send. A later pass covers many of those bots talking at once. You can add a second profile for alerts so scheduled jobs do not bury the live chat. That is optional — Telekit does not ship an alerts bot. Bridged turns never inherit it. telekit send --profile alerts "…" --yes Persona is per bot. Skills are global. See Skills.

​
Users on each bot

Manage a profile’s users with telekit bot-users list --profile alerts. The list includes owners and members, their numeric IDs, and whether each account is allowed, paused, or disabled. See Access for the message-based add flow and all JSON commands. Adding, removing, or pausing a user applies only to the selected profile. Members are always enabled in the backend. Individual users can be paused while their saved grants stay intact. Owners can be paused too. Removing a person blocks their private and group access on this bot and keeps their saved conversations. It does not remove their access on other bots. If you change the bot token or disable or remove the profile, its discovery session becomes invalid. Use the correct running bridge before trying again.