The recommended Oracle Analytics security model is to manage permissions through Application Roles . An application role represents a set of permissions determining what its members can see and do in Oracle Analytics Cloud. Administrators can assign users, groups, and even other application roles as members, allowing authorization to be administered centrally.

This is considerably more scalable than granting permissions individually. For example, an administrator can create or use an application role for Finance Analysts, assign the required analytics privileges and content permissions to that role, and then add all qualifying users to it. When staffing changes occur, administrators modify membership rather than repeatedly redesigning permissions.

Oracle's current guidance explicitly states that it is a best practice to assign permissions through application roles. Predefined roles such as BI Content Author and BI Consumer provide standard capabilities, while user-defined application roles can be created for organization-specific requirements.

Separate catalogs and duplicate dashboards would create unnecessary management overhead. Database accounts don't replace Oracle Analytics application-layer authorization.

Therefore, assigning users to Application Roles is the correct scalable approach.

Reference Topic: Managing Administration, Security, and Performance — Application Roles

===============