Integration Access Control, Filtering and Backup using Package Structure

Description

Specifically when we position OIC as a LOB User centric iPaaS, it becomes extremely important that one LOB user should not be able to access other LOB's integration.

Use Case and Business Need

Would like to suggest a improvement where the access is controlled by package. Through use of package, following things should be implemented.
1. List of integrations by package groups. 
   Currently we have ore than 300 integrations, some in dev version, some in UAT. we follow package naming convention as 
   xx.fin.ap, xx.fin.ar, xx.prj.costing, etc (where xx is company name)
   Listing integrations following the directory-like package hierarchy greatly helps in organizing integrations