Permissions in Ventoo Case Management

Ventoo Case Management ships four assignable permission sets. They govern basic table and page access (BC level). In addition, role capabilities and case visibility control at the app level who sees which cases and what they may do (see Permissions and visibility in Ventoo Case Management).

The four permission sets

Tiers (inclusion hierarchy)

The sets build on each other:

Consultant  (base)
   ├─ Manager   (includes Consultant)
   ├─ Finance   (includes Consultant)
   └─ Admin     (includes Manager + Finance)

Consultant – day-to-day work

Full access (RIMD) to the operational tables: cases, activities, relationships, tasks (incl. checklist), attribute values, notes, filters, and saved filter sets. Read access to configuration tables (roles, processes, attributes, billing profiles, naming) and read access to case ledger entries. Access to the operational cards, lists, the role center, planning, the API pages, and the evaluation reports (Case Overview, Activity, Utilisation, Task). Scopes and engagements: read and modify.

Manager – additionally structure and billing view

Additionally RIMD on parties, scopes (incl. items), engagements, and relationships, plus full planning. Case ledger entries: read and modify (view of billing data, but not running billing). Access to the billing view pages (Case/Engagement/Scope Billing) and context reassignment (via the controlled, audited codeunit).

Finance – run billing

Additionally RIMD on billing document lines and the right to create case ledger entries (run billing). Full access to the billing pages, the billing codeunits, and the Billing Batch and Revenue reports.

Admin – configuration

Additionally RIMD on all configuration and setup tables (setup, roles, processes, naming, teams, dimension priorities, attributes + groups + dropdown values, party-type assignments, attribute assignments/permissions, billing profiles, user mapping, role capabilities, scope schemas). Access to all configuration pages, the setup wizard, and the translation codeunit.

Assignment

Assign users the appropriate set (BC: Users → permission sets, or via user groups/security groups). In addition, each user should be mapped to a party and visibility level in the User Mapping list so that case visibility works correctly.

Access control via AccessByPermission

Some UI elements are additionally bound to specific rights via AccessByPermission. Examples: the billing view is tied to the modify right (M) on case ledger entries, and running billing to the insert right (I). So a Manager sees billing data without being able to trigger billing, while Finance can do both.