Ahh i see. So its still not usable for this: What if AI Chat was a field? Or an automation where builder can make their own AI Chat embedded where needed? - #10 by RonMakesSystems
If you have it set up (like in the demo above) where the users can make a their own prompts, they will be able to change it and get back data they need every month.
The ideal scenario to me is that the admin has the ability, per rule, to set the auth to be the “User who triggered rule” (like if building a chat bot), or “Admin Access” / or give the chat bot specific access controls.
For automations that are triggered by a user, (not scheduled) in any case, it would be good to give it that access and not the admin access.
The part it gets tricky is chaining rules together, you’d need a better mechanism to find out who was the original person who ran the rule, or make for better no-code automations where you no longer need daisy chaining.
Not easy stuff to do at all! But would be good to think about in the coming future with this.