BOTLOBBIESCan friends in my party control the bot?
Being in the same party does not make a friend the bot's owner. Website actions use the authenticated owner's access, and supported party commands can also check the configured player identity before accepting an instruction.
Understand which permission is being checked
There are several distinct permissions in a group session: who leads the Fortnite party, who owns the website account, and which player is associated with the bot. A friend may be able to invite another player through the game without being allowed to change your saved bot settings. The owner-only command handler explicitly compares the sender with the configured owner. Do not assume that receiving a party invitation also transfers the ability to issue every bot command or manage billing.
Coordinate appearance requests without sharing access
A practical arrangement is to let one person operate the panel while friends suggest changes in voice chat or normal conversation. Apply one choice, check it in the lobby, and move on after the result is visible. This avoids a stream of competing instructions and preserves a clear account owner. Never use a shared password, email code, or Epic authorization code as a shortcut for collaborative outfit selection. Those credentials control more than the cosmetic feature the group is discussing.
Read rejection messages in context
If a command from a friend is ignored or rejected while the owner's command works, that can be the expected permission boundary rather than a broken connection. First identify who sent the instruction and which bot the panel currently selects. A connected bot should not be restarted solely because it declined an unauthorized request. If the owner also cannot act, check the current access state and the exact response. Record the command name and time without copying private account identifiers into public chat.