1) Data Roles are VDB-centric.
2) There can be ZERO or more data roles within a VDB.
3) A data role can define permissions (CRUD) on models, tables and columns that span "Models".

A) VDB Editor needs to provide some Data Role access on the basic editor page. Maybe the "User Files" bottom group is broken up into two panels, the RIGHT panel being "Data Role". Panel would allow "ADD", and "REMOVE", but also "EDIT" buttons.

Create a Wizard that can CREATE AND EDIT a data policy.

Wizard/Dialog should be able to Select any of the models contained in the VDB (that allow entitlements. Maybe just relational?)

• Contain an Editable "Name" field.
• Contain an Editable "Role Name" field.
• Contain a Tree-Table with contents of selected Model AND 4 checkboxes to handle CRUD values
• Enablement of CRUD check-boxes should be driven from "Supports Updates" values for both Virtual and Physical relational table data.