In ODC, the traditional 4-layer canvas has been replaced, and the development methodology now involves "Applications" and "Libraries" instead of "Modules".

ODC has two primary elements: apps and libraries. Roles and entities are exclusive to apps, and it's important to note that roles cannot be made public. Web Blocks can only be made public within a library. Apps can use elements from both apps and libraries, while libraries can only access elements from other libraries.

ODC hasn´t yet made available user and roles management API, and, by design, there is no direct access to system entities like User_Role, Role, or User_Effective_Role entities, making it necessary to find alternative solutions for role-based functionalities.

A crucial element in most applications is a role-restricted menu. In ODC, where roles cannot be made public, having a menu that intelligently detects user roles and displays relevant items is essential, especially in applications with multiple concepts and distinct roles. 

On this session João Fernandes will explain an approach to develop a role-restricted menu in ODC considering these constraints, while not having yet available API for user and roles management.