This is not easy to do, since tasks are not scoped per organization. I believe filter can be finegrained by tasks attributes including owner, but you'd need to create separate filter for each user, since we can't define a condition such as "owner = $current_user".

Personally I consider tasks page as maintanance tool and would not expect non admin users to interact with it. If users need cancelling, it should be provided by page that generates the tadk, e.g. rex jobs have their cancel button.

Moving to tasks component to consider.

This depends on the definition of "non admin", or "admin". Multi tenant environments do not simply have adminstrators, they have administrators responsible for the system, and administrators local to the tenant (organization). Delegation of responsibilities to the organizational level is vital, as is separation. 

There are worse separation issues than this, with severe security consequences. But regarding the advertised features, everything breaking the borders of tenants is more than just a feature nice to have.

I understand your point and you're right. By admin I meant system administrator of Satellite. In ideal case, organization admin should have no need to visit tasks page. Or we should start scoping tasks by the context (organizaton/location) in which they have been created. Similarly to audits, where we have the same problem I believe.

*** Bug 1322566 has been marked as a duplicate of this bug. ***

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.