# Employee - Stakeholder
## Overview
The employee stakeholder flow consists of 2 independent screens and 1 application details page. Users have access to this flow using links in the Inbox and the Search application page.
## MDMS Data
The stakeholder MDMS data is used to filter views and service types displayed on the screen in accordance with the existing user role. The [TradeTypeToRoleMapping ](https://github.com/egovernments/egov-mdms-data/blob/DEV/data/pb/StakeholderRegistraition/TradeTypetoRoleMapping.json)MDMS data is also used to filter views based on the selected business service.
## Localization
The localization module used in the OBPS module comprises rainmaker-bpareg and rainmaker-common. The rainmaker-bpareg is initialized for module localization.
## API Role Action Mapping
User access to the stakeholder flows and BPAREG business service is role-based. Roles can be - `"BPAREG_EMPLOYEE", "BPAREG_APPROVER", "BPAREG_DOC_VERIFIER", "BPAREG_DOC_VERIFIER"`
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.digit.org/local-governance/access/local-governance-stack/online-building-plan-approval-system-obpas/obpas-service-configuration/obpas-digit-ui/employee-stakeholder.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.