In many organizations, FME Flow is managed centrally and engine resources are shared across different teams or departments. However, FME Flow currently does not offer any permission control on engine queues.
At the moment, when a user/author has access to view queues, they can see all queues defined on the FME Flow instance. This can be problematic in environments where engine usage needs to be compartmentalized.
Example use case
The IT department is allowed to use 2 specific engines/queues.
The GIS team is allowed to use 3 different engines/queues.
However, because queues are not permission-restricted, any user can select any queue when creating schedules, automations, or running workspaces if they have access to the advanced part.
Suggested Improvement
Add the ability to control which engine queues a user or role can see and use.
This would allow administrators to:
- Restrict access to specific queues based on user roles or groups.
- Prevent users from unintentionally using engines they are not supposed to access.
- Improve resource isolation and governance in multi-team or multi-department FME Flow environments.
