You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the bot can't find the user in the DB and says, "sorry, you don't have access, send /requestAccess and wait"
user sends /requestAccess to the bot
bot says "thank you, I notified the admins" and sends a message to the admins, initiating a conversation to choose whether to accept or reject the request
admin accepts the request: user is created in the DB with the default permissions / admin rejects the request: nothing is done
user receives a notification saying they have been granted/denied access to the bot
The access requests could also be deactivated. In that case, we stop at step 2 and the bot just says "sorry".
To simplify admins work, we could store the last 100 users who sent /start and didn't have access with their usernames and ids in a file, so an admin can just send /grantAccess username to the bot, which would pick the right ID in the file.
The text was updated successfully, but these errors were encountered:
/start
to the bot/requestAccess
to the botThe access requests could also be deactivated. In that case, we stop at step 2 and the bot just says "sorry".
To simplify admins work, we could store the last 100 users who sent
/start
and didn't have access with their usernames and ids in a file, so an admin can just send/grantAccess username
to the bot, which would pick the right ID in the file.The text was updated successfully, but these errors were encountered: