Skip to main content

Manage your team: Involve colleagues in the care of an AI expert

If you don't work alone on creating, managing, marketing or supporting your AI Expert, but have a team of colleagues or a virtual assistant, for example, you can assign them special permissions within the BuddyPro platform so they can help you effectively.

24.1 How to add a member to your team

To enable a member of your team to use certain administrative commands and help you manage your instance, follow these steps:

1. The collaborator must initiate a conversation with your AI instance.

First, your colleague or assistant needs to open a chat with your specific BuddyPro instance in Telegram. You can send him/her a standard invitation link (generated, for example, using /generateBuddyProInvite:{trialMessages}:{code}:{usersLimit}). Be sure to set up enough trial messages ({trialMessages}) in the invitation for his/her needs if he/she does not already have an active subscription.

2. The collaborator will find out his/her unique Telegram ID ({userId}).

Ask your collaborator to type and send the following command in the chat with your AI instance:

/myid

Your AI instance will respond and display his unique numeric Telegram ID. Request this ID from him — you will need it for the next step.

3. You (as the master instance owner) will assign team permissions.

In your chat with your AI instance, enter the command:

/addUserToTeam:{userId}#{your_buddypro_telegram_bot_username}

Replace {userId} with the numeric ID that your colleague has given you.

What permissions does the team member get?

The team member with the assigned permissions will be able to use some of the admin commands that you, as the primary owner, use by default. Typically this includes:

  • Running commands to update know-how and roles (e.g. /update, /updateRoles).
  • Using diagnostic commands (e.g. /lastRole, /showCost).
  • Generating invitations for new users (/generateBuddyProInvite:{trialMessages}:{code}:{usersLimit}).
  • Setting some AI instance parameters (e.g. /setSupportEmail:{email}, /setTrialEndedMessage:{message}).
  • Managing users and their subscriptions (e.g. /getInfoAboutUser:{subscriptionId}, /disableUser:{subscriptionId}, /giveExtraMessages:{subscriptionId}:{extraMessages}).

What can't a team member do?

  • A team member cannot change the master owner of an instance (/setProOwner:{userId}). This action is reserved only for the current master owner.
  • He or she cannot perform some other very critical operations that could compromise the security or integrity of your instance, unless they are explicitly allowed for team members.
Trust is key

Only grant team permissions to people you fully trust, as they will gain quite extensive ability to influence and manage your AI instance and its users!

24.2 How to remove a member from your team

If you need to remove a team member's extended admin permissions, use the command:

/removeUserFromTeam:{userId}
  • Enter the Telegram ID ({userId}) of the collaborator you want to remove from your team.
  • After executing this command, this user will be a standard user (without special admin rights) for your AI instance again. His access to the instance as a regular user will depend on whether he has a valid subscription or an active trial period.

24.3 Managing system message recipients

Your BuddyPro AI instance automatically sends system messages — internal notifications about important events related to instance and user management. Typically, these include alerts such as payment of the second invoice for non-activated subscriptions, an attempt to activate a package without an active subscription, and other operational messages.

Screenshot 2025-12-05 at 10.39.21.png

Screenshot 2025-12-05 at 10.38.38.png

By default, these system messages are delivered to the owner (primary instance owner). However, you can also forward them to additional people (e.g., a teammate) so they can handle admin tasks for you.

Who can manage recipients?

Only the owner can add/remove system message recipients. Team members do not have these permissions.

Requirements

  • A new recipient must first be a team member (see /addUserToTeam).
  • Adding a recipient does not automatically remove the owner from the recipients — if you want notifications to go only to the delegated person, you must remove the owner manually.
  • The owner cannot be removed if they are the only system message recipient.

How to add a system message recipient

/addSystemMessageRecipient:userId

How to remove a system message recipient

/removeSystemMessageRecipient:userId
info

If you remove yourself (the owner) and then remove all other recipients so that no one remains, the owner is automatically set again as a system message recipient (to ensure there is always at least one recipient).

How to list the current recipients

/listSystemMessageRecipients

Frequently Asked Questions (FAQ)

  • How many team members can I add? The system does not currently provide an explicit limit for the number of team members.

  • Is there any additional cost to add a team member? There are no additional licensing fees associated with adding a team member per se. However, the cost of AI credits applies to all instance activity, including that performed by the team member.

  • What happens if a coworker sends me the wrong Telegram ID? If you enter an invalid ID, the command will likely fail. If you enter the ID of another existing user, you accidentally assign permissions to the wrong person. Therefore, it is important to verify the ID carefully.

  • Can a team member also manage their own BuddyPro instances, if they have any? Yes, a team member's permissions only apply to the specific instance you have added them to. His own instances (if he has any under his license) are managed separately.

  • If I remove a team member, will they completely lose access to my AI instance? By removing him from the team, he will only lose extended admin privileges. If he had a purchased subscription to your instance or an active trial period, he will still have access to it as a regular user. If he didn't have access (e.g. the trial you gave him for testing purposes has expired), then he will no longer have access or special permissions to the instance once he is removed from the team.