If a customer has highly sensitive data and really needs the most controls from an access standpoint, does Anaplan recommend….
It depends upon how that data needs to be consumed. If that data needs to do some analytics in the spoke model, then you can store it in a different workspace and pull the aggregated values into the spoke, This way, your data is secure and you're getting required insights from it in the spoke.
Bifurcating your workspace facilitates the ability to control your admin access - for example you may allow more builders/admins in a DEV or less sensitive workspace while limiting access on an as needed basis for more sensitive models.
Typically, a customer will only have a single tenant.
Below is a quick view of different levels of security within Anaplan, you can use a combination of tailor the user's experience to only see data which is appropriate for their usage:
Thank you for the responses. I still feel like having a seperate tenant for ultra secure data offers an additional level of security.
Senario A - If you split a sensitive data model into another tenant (meaning 2 total tenants), you might be able to have only 2 tenant admins in other tenant due to it being smaller. Meaning 2 people who have power to give people access to sensitive data
Scenario B - You have 4 tenant admins in 1 tenant that has sensitive data. These 4 tenant admin are needed given the size of the organization. Those 4 tenants could give access to the sensitive data workspace.
From a security standpoint, scenario A is more secure.
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!