> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/develop/architecture.md).

# Architecture

### **Partner Management Service**

**Partner Management Service** provides various partner services like onboarding partners and providing partner data to other modules.

The diagram below illustrates the relationship of this service to other MOSIP services.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-fba82de9e13d3ddfb0df35d8fffa96f97c7cb382%2Fpms_arch.png?alt=media" alt=""><figcaption></figcaption></figure>

1. Certificates of partner are uploaded to [Key Manager](https://docs.mosip.io/1.2.0/modules/keymanager) as part of onboarding.
2. Registration processor fetches ABIS datashare policy from PMS.
3. PMS sends notification messages to partners via notification service (of Kernel).
4. Audit logs are logged into Auditmanager.
5. [ID Repository](https://docs.mosip.io/1.2.0/modules/id-repository) fetches credential data share partners and their polices from PMS.
6. All PMS data is stored in mosip\_pms DB.
7. Certificates of Authentication Partners are sent to IDA module as IDA runs independently. The certificates are shared using [Datashare](https://docs.mosip.io/1.2.0/modules/datashare) (which futher uses Websub to share data with IDA).
8. PMS invokes the client management endpoint of eSignet to register OIDC client

Rest of the content can be referred to here: <https://docs.mosip.io/1.2.0/modules/partner-management-services>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services/develop/architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.