test mode would Make It Only Usable By The Collaborators and would let the collaborators test the bot features (even without premium(i would wish)) this would be particularly useful for me bc i like to test my bots features before allowing others to use the bot (now i know you might say “use collaborator Only” but thats only on slash commands (yes i know “if user is collaborator” exists but im trying to say it should be a feature in the power settings or something like that) i know my explaining sucks, but i dont know how to explain it better
maybe make a database with all the userids that should have access to it, and add an if database does_not_contain authoruserid
exit Flow
This would work, but some stuff really wouldn’t work with this method. The best implementation I can think of would be a separate bot. Magic has confirmed here that text-based editing is in the works, which would let you copy-paste stuff between bots. Magic also confirmed this might be coming, which would let you do a test bot easily.
This won’t be added. Consolidating the executing user id across all triggers and setting up an allow/denylist is difficult at best and not even possible at worst (depending on the trigger) and having this as a global setting might create a false sense of security.
As others have mentioned, there’s plenty of other solutions for allow/deny-listing specific features or even entire bots for testing (you can have a custom block at the top of each flow, etc). The migration tool will make this a lot easier in the future as well.