Is it possible to have an action that some users can trigger, but cannot discover for use in their own workflows?
@mmagid I don’t think there’s a way to hide actions or control their visibility.
I don’t know under what circumstances you want to make the Action available for users or not. But it you want it only to be triggered via a specific Workshop application, perhaps you could include a hidden parameter that needs to have a specific value only set by that workshop?
It’s not really a secure method though, as I’m not sure there’s any way to hide that ‘secret’, and someone could find it or create their own Workshop that does the same. But it would prevent users from triggering it by accident from the drop down Actions menu.
An alternative - but I’ve not tried this - might be omit the object type ID when using a backing function in the @edits() decorator. The input would still be that object in the function, but I think Foundry would then not automatically link the Function/Action with the object, sort-of hiding it…perhaps?