Roles, Functions, and Feature Toggles Oh My

[lpciferri]

We're at a point where Caseflow products are converging more obviously. We have users using more than one application at a time, and are building ways for them to flow seamlessly from one product to another (e.g. from Queue to Reader). We also have quite a few feature toggles in Queue that might be able to be consolidated (already started with https://github.com/department-of-veterans-affairs/caseflow/issues/5474). This issue includes an idea for organizing our users and functions.

CSEM includes "roles" and "functions". In our code, we use the term "role" to refer to what CSEM defines as a "function". For instance, HearingPrep is a role in our code, but a function to CSEM.

Currently, most applications use the "user" role, but we have different functions related to our applications. As Caseflow adds more products, we want our CSEM roles and functions to accurately reflect our users and products.

This is scoped to only include Board users, and excludes Certification and Dispatch.

Ideas

• Use a template for CSEM to see, by Role, what Functions a user should automatically have access to. The CSEM initiator would not be able to edit the Functions because of the template.
• For example:

Role	Functions
Attorney	Reader (inclusive of Queue)
Judge	Reader, Hearing Prep

Previous discussions about this

• Post-Standup discussion, recognizes merits of using CSEM/CSUM while having control over System Admin role - https://github.com/department-of-veterans-affairs/appeals-pm/issues/1540
• Follow-up, desire to use existing BVA and VBA roles and functions, though they may not be specific enough - https://github.com/department-of-veterans-affairs/appeals-pm/issues/1339

[lpciferri]

closing - duplicate of https://github.com/department-of-veterans-affairs/caseflow/issues/5549