Seggregate data per role/user

We are working on a project that has data from a very large organization (300+ teams, 3.000+ people) which has a hierarchy and we would like to be able to seggregate the data that each person/group can see using 1 project.

We would like to be able to have 1 project for everyone, but be able to give access to the data that each person needs for privacy matters to all items of the project (flow, prescriptive, analytics, alerts...). So we can maintain 1 proyect and each person gets access/alerts... of the items they are interested on.

Organizational Requirement

The client organization has:

5–10 directors

10+ managers working with each director

5–10 area leads working with each manager

Analysts within each unit/team (1 per team)

In practice, this means we will need separate users for each director, manager, area lead, and analyst at the lowest level of the hierarchy.

What We Need

1. Data Access Segmentation

Each person must only see the tickets, cases, and SLAs that fall within their scope of responsibility (director, manager, area lead, analyst).

User/role filters and views must be separated from those of other users to ensure privacy and prevent cross-visibility between units.

2. Alert Segmentation

Each person must only receive SLA alerts related to the tickets/cases their team is working on.

Example: A manager should receive alerts for their own team, but not for teams managed by other managers.

3. Dashboard Segmentation by Role

We need to configure which dashboards are visible based on the role:

Executives/Directors: High-level, consolidated dashboards (executive dashboard).

Managers: Operational dashboards to monitor SLA compliance and performance.

Area Leads: Dashboards focused on local workload, causes of delays, and pending cases.

Analysts (by unit/team): Complete technical dashboards with all available KPIs and filters to build specific analyses for their unit.

4. Two Main Access Layers

Executive Role → Access only to summary dashboards (strategic view, SLA risk, costs, rankings).

Technical Role → Access to all dashboards and full detail (process compliance, causes of pending cases, workload, automation analysis).

Within the technical role, each analyst per unit/team must be able to apply specific filters to analyze their scope without affecting what other analysts, managers, or directors see.

Expected Impact

Scalability: Allows a single IBM PM project to support thousands of users in a structured way.

Privacy: Ensures each role/person only sees what is relevant to them, both in dashboards and alerts.

Efficiency: Avoids duplicating projects for each unit or department.

Adoption: Makes dashboards relevant for each role, from executives to analysts.