Open Settings > Operators on an account that uses bots and the list is longer than your team. That is expected. Every bot gets its own operator record, because a bot has to appear as a sender on a conversation in the same way a person does.
The extra entries are not colleagues you have forgotten about, and they are not something to tidy up.
How to spot a bot
Bot records sit after the people in the list, and each one is marked with (bot) under its name. The name is the bot's own name, so a bot called Concierge appears as Concierge (bot).
The record carries a generated email address rather than a real mailbox. Nobody receives mail at it, and it is not an address you or a colleague can log in with.
What a bot's record holds
Open one and you see less than you would on a person's record.
Profile. The bot's name and its generated email address.
Accessible Apps. The properties the bot works in, set the same way as for a person.
That is the whole record. There is no role, because a bot does not open sections of the platform the way an operator does. There is no two-factor authentication, because nobody signs in as it. There are no notification settings, because there is nobody to notify.
Where a bot's record comes from
You do not create these by hand. Creating a bot creates its operator record at the same time, and the record is named after the bot. See Creating a webhook bot and giving it team access for how a bot is set up.
A bot can be de-activated in the same way as a person, and then appears under Inactive Operators at the foot of the list. See Inactive operators.
What this does not do
Accessible Apps is not the same as team access. The properties on a bot's record decide which properties it belongs to. What decides whether it can see and answer a particular conversation is the team it is on and whether the ticket is assigned to it. That is covered in What a webhook bot can do in the Unified Inbox.
Editing the record does not change the bot. The name and the property list are operator settings. How the bot behaves, what it is allowed to send and what it knows are set where the bot itself is configured.
It is not an invitation. Bot records are created by the platform, not through Invite or + Add new, and there is nothing to send to anyone.
What to do next
If you are setting a bot up for the first time, start with Creating a webhook bot and giving it team access. If you are working out why a bot is not answering, see Why your webhook bot is not responding.
For the rest of the Operators screen, see Adding and managing operators.
Getting help
Open Help at the bottom of the left menu and choose Talk to Us, or email support@bookboost.io.