Restricting access to global connections in pasteviews but not in integrator Merged

Since changing Excel to use Jedox web forms, all the global connections appear in the list. This means that a user can do a pasteview from any of the global connections in the list with the credentials that are associated with that connection which could be admin credentials.

To work aroudn this, permissions on the global connection can be removed. However, this then means that any action buttons that call Integrator jobs using that global connection will now fail. However, this could be a very valid scenario.

Example:

I want a user to be able to use an action button which triggers and Integrator job to reload the data in from the ERP system. This data gets written to the income statement cube.

That user should not be able to manually edit data in the income statement cube in a pasteview as all data in this cube should only come from the ERP system. Therefore we remove write access from the user on this cube.

We then create a global connection with admin credentials which is what the Integrator job uses and then the action button is linked to this global connection.

However, we then find out that the user can now do pasteviews using this global connection and start to edit the income statement cube which they should not be able to do. Therefore we remove access from the global connection for the user.

Now, the action button calling the Integrator job fails.

Currently the only way you can do this is to use static connections within Integrator and don't use global ones. However, if you have say 20 Integrator projects and change the password, you then have to go and update all 20 projects and not just 1 place.