Capture User manually kicking off project on server


We have a project that we want to run on the server, not on a schedule, but only give certain users the ability to run the morph.

We thought about somehow having a validation parameter in the morph that could check the user who is trying to run the morph on the sever, but not exactly sure how this would be configured.

Or perhaps limiting the visibility of some morphs to a certain list of users?

Does anyone have any ideas?

The canonical way of providing access to only a subset of users would be creating a separate space for them.

Alternatively, if the space has AD authentication configured, you can use the system(‘identity’) function. It allows creating custom authorization.