Hello everyone!
We are trying to understand how to manage the cloud database security in our Appian Cloud instance. We will have multiple teams working each one on the applications of its own area, and we don't want everybody to see all the tables of Appian. We were thinking about telling developers to ask the administrators to create a different db schema for every application so that every developer could see only the tables of the applications he was working on. However we read the following sentence in the following page of the documentation.
"The majority of your data should be stored in the default "Appian" schema. We recommend that you only create additional schemas when your applications need data segregation and isolation."
https://docs.appian.com/suite/help/21.4/appian-cloud-database-administration.html#appianprocesscreatenewschema
Why does Appian recommend to store the majority of the tables in the "Appian" schema, which is visible to all the developers? Only because if a table is in the Appian schema it can be shared between different applications or there are other reasons, such as performance issues or similar?
Thank you to all will want to help us!
Discussion posts and replies are publicly visible
That's just a recommendation. If you "need" isolation, just do it.
docs.appian.com/.../appian-cloud-database-administration.html
Agreed with Stefan, I wouldn't read too much into that sentence. I think what it likely means is that in many cases the data isn't especially sensitive, so the default would work fine. However, there's are no issues with exclusively using separate schemas, just that it will require an extra step to set up each schema before you start using it
Ok, perfect! Thank you for your replies!!