Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!
The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Server Ideas

Share your Server product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Chinese Wall Requirements in regulated environments

In regulated environments, like banks, there is a requirement to fully segment Alteryx Jobs so that people on either side of a Regulatory Wall cannot access each other's canvasses or results.

 

As an example:

- Public vs. private side in Broker/Dealer banks

- Compliance or HR or Finance need to be segmented from all other areas in most banks

 

What is needed here is for any canvasses belonging to each of these walled-off areas to be controlled so that they cannot be shared across the wall, and results cannot be viewed across these areas.   This also means that the Gallery Environment needs to be capable of being segmented fully within 1 installed environment.

 

CC: @rijuthav @jithinmony @HengHe @RajK @ydmuley @revathi @Deeksha @MPistone @Ari_Fuller @Arianna_Fuller @JoshKushner @samnelson @avinashbonu @Sunder_Sriram @Rahul_Thakur @Rahul_Singh

 

 

8 Comments
SeanAdams
17 - Castor
17 - Castor

We work in an environment where there needs to be strict partitioning between both workflow and data assets for regulatory reasons (they call this the Chinese Wall).

So - we'd like to have the capability to segment gallery assets in a way that we have one user-base; one set of licenses; one set of administrators; one server - but the ability to segment assets and permissions into domains.

 

For example:

- People who work in Private Wealth should not be able to see flows or assets which belong to the broker-dealer since this would be a risk for insider-trading

- People who work in the merchant bank should not be able to see what's going on in the broker dealer or the Private Wealth business.

 

However, we do want to be able to administer this as one so that we can see server failures, error logs, etc.

 

Finally - there will be a very small subset of assets (e.g. shared macros) that can be shared across these domains, but they have to be tightly controlled).

 

cc: @avinashbonu @revathi @Deeksha @Ari_Fuller

MattB
Alteryx Alumni (Retired)
Status changed to: Under Review

Thanks @SeanAdams for another great idea. Would the concept of sites work for this segregation? Using your example, you would have one Alteryx infrastructure to administer with one site for Merchant bank and one site for Private Wealth. It would be similar in concept to a multi-tenant system, which is a fundamental aspect of a SaaS solution. Tableau currently does this with sites -> What is a Site? .

adrianloong
11 - Bolide

+1 , much needed in regulated financial services enviroment. Currently i believe collections is the way to do this however would love to have an easier way to do this similar to tableau sites

MattB
Alteryx Alumni (Retired)
Status changed to: Under Review

Hi @SeanAdams,

 

Thanks for sharing the idea. I recently updated another post where my reply is relevant to this idea so I'll link that here.

Collections Administration

SeanAdams
17 - Castor
17 - Castor

Hi @MattB

 

This could be done with sites like with Tableau - with the proviso that we'd need to segregate any underlying data storage too.

 

The administrators can act across sites (we call this "being wall-crossed") but it is important that folks cannot access data or cached workflow results in any way from the walled-off assets.

 

 

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: Under Review

Updating this idea's status back to Under Review, to be in line with past product updates.

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: Under Review

Updating this idea's status back to Under Review, to be in line with past product updates.

KylieF
Alteryx Community Team
Alteryx Community Team
Status changed to: Accepted

Thank you for contributing to the Alteryx Community! This idea has been accepted and is now on our road map. We'll update the idea status again once we are close to implementing the idea in the product.