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 ? ) 

The link you provided isnt working 

Hi chandra,

the link which you provided is for staging environment of community, which is not accessible for us. Could you please provide correct url?

Thank you

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.

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 )