Bypass approval if custom command is executed

Question

Hi team,

we have a basic approval setup for a specific group

I would like to bypass this, in case a specific custom command is executed and trying to add a member to this group.

Is this somehow possible? I tried to play around with "If the initiator is xxx" but had no success yet.

Answer 1

Hello,

Unfortunately, there is no such possibility. However, thank you for the suggestion. We forwarded it to the corresponding department for consideration.

Comments

Hello,

Please plus one for me on this Idea. We have a similar need where we try to ensure users cant modify certain fields without it being under a pre-built command us admins make. There is some cases where a full command is not needed to be ran. But if we have a group change that is part of a command, we would want to auto-approve that action, as to us, that commands hold paramaters like "Ticket Number for Justification" so these are considered auto-approved as they ask the questions they must have answers for. But if we have a user who adds the group any other way in adaxes, outside the command, we want approval to go out so they know it was attempted for one, but also to approve or deny the "One-Off" add.

I full agree with the OP, this would be a nice Quality of Life Selection. Maybe in the logs it shows initator is XYZ User still as it does today, but adds somewhere ON BEHALF OF "ABC" COMMAND

This would have to fully rely on adding in your logging "Command Reference" or something that is tied. I know the icon on the logging page shows the gear icon to indicate this so Adaxes somewhat knows it was as part of a "Series." I do understand that work could take some time. But it would benefit for these certain use cases.

Thanks for all the great work/improvements/support!

---

Hello,

Sure, thank you for a detailed explanation of the workflow you have.