Hub: Execution Resource not assigned but still available to and executable for the team

Hi,

I noticed after revoking access to execution resourcee that they are still available to the team.

It appears that despite revoking access, execution also can be initialed:

PS: It might be good to improver the visual distinctiveness of an assigned and unassigned executor like by decreasing the opacity of unassigned to .5 and append “ (not assigned)“ to the executor name:

Best
Mike