Use Metamodels as permission containers for domain separation

Problem Overview

Even within the same Application, different user groups may need access only to certain datasets/entities/import templates (e.g., Finance vs HR). Without a clean permission boundary, users may see datasets they shouldn’t.

Solution

In WOODY.IO, Metamodels can serve as permission containers: assign Roles to Metamodels so only a subset of users can work with the defined information (including Import Templates).

Configuration

1. Create/maintain separate Metamodels per domain (Finance, HR, etc.).
2. Assign Roles to those Metamodels so only authorized users can see/use their Import Templates. 
3. Keep shared infrastructure (Connections, Application SP) at Application level, while controlling data exposure via Metamodel permissions.

If you have any further questions, please feel free to Contact Us.