Multi tenancy - data schemas

We are analyzing the feasibility of going for multi tenant approach to have common pega platform for multiple LOBs . Here the question is about data separation / security / performance aspects . Can we have separate data schemas for each tenant or the single data schema is shared between the tenants ? If it is shared , as several OOTB tables are common in a data schema ( Like pc_assign_** tables ) ,

(i) How to prevent other tenant from accessing / viewing the other tenant records

(ii) How to reduce the impact due to performance issues caused by one tenant on the other ( Caused by several factors like overload of data / lack of archival process etc)

***Edited by Moderator: Pallavi to update platform capability tags***


Keep up to date on this post and subscribe to comments

February 4, 2019 - 8:00pm


Please refer the attached multitenancy support guide which give full information regarding the security.

To maximize performance, minimize the number of customized rules and data classes in tenant region.


February 5, 2019 - 12:45am
Response to chandrasekhar_g

Thanks for the the reply Chandrasekhar . I referred administration guide before posting this but it is not much illustrative & did not mention how it is different from Pega's role based security model which is applicable even in non-multitenant applications . I am more interested in knowing how to separate the data between the tenants and what is meant by "tenant specific customizations" ( e.g can we have separate pc_assign_workbasket table or the entire new data schema for each tenant without adding too much complexity to the platform ? ) 

May 14, 2019 - 10:40pm
Response to chandrasekhar_g

The link you provided isnt working 

February 10, 2019 - 7:47pm


Please refer 3rd page of above document (multitenancy administration guide) which explains about pega platform multitenancy.

February 11, 2019 - 2:15am
Response to chandrasekhar_g

administrative guide just gives an overview , can you share some details of how to achieve  multi tenancy using approach 3 . I dont see any documentation for this.

February 12, 2019 - 2:14am
Response to chandrasekhar_g

Can we get more details on implementation ? As we are planning this to implement for one of our clients , we need more details indicating how each of the component works ( e.g. : How the database table level security is achieved in a scenario where one tenant writes Obj-browse method which fetches all the records including other tenants data )

February 14, 2019 - 1:37am
Vidyaranjan | Community Moderator | Pegasystems Inc.

May 14, 2019 - 10:43pm

@vamseekk did you any solution for this.

I am looking at multi-tenancy with Data Isolation