# Datashare

## Overview

The DataShare service is used to share data with other entrusted services and partners. The mechanism shares are the following:

1. Retrieves and stores data to be shared in [Object Store](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/persistence/object-store) and returns a Datashare URL.
2. It fetches data from the Object Store when the Datashare URL is called.

The sharing of data is controlled by the [Datashare policy](https://docs.mosip.io/1.2.0/support-systems/partner-management-services/pms-existing/partner-policies#datashare-policy).

Data is encrypted before sharing it with partners. Learn more about [datashare encryption](https://docs.mosip.io/1.2.0/readme/principles/privacy-and-security/data-protection#datashare).

The relationship of Datashare Service with other services is explained here. *NOTE: The numbers do not signify the sequence of operations or control flow. Arrows indicate the data flow.*

![](https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-df5bbd57f472881d655d4f24aef395a376a3bf97%2Fdatashare.png?alt=media\&token=3d7f57a5-2b2e-4f3d-a3be-aef2344d3dbe)

1. ABIS Handler Stage creates datashare for ABIS.
2. Manual Adjudication Stage creates datashare for adjudication.
3. Verification Stage creates datashare for verification.
4. Datashare Service calls [Policy Manager Service](https://docs.mosip.io/1.2.0/support-systems/partner-management-services#policy-management-service) to get the policy for creating shares.
5. It calls the [Keymanager](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/keymanager) Service to encrypt data as per policy.
6. Stores datashare inside [object store](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/persistence/object-store).
7. Retrieves datashare from the object store when the datashare URL is called.
8. External systems like [ABIS](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/abis), Print System, Adjudication system etc. calls Datashare Service to get the datashare.
9. Print Service creates UIN PDF and uploads to datashare through Credential.
10. [Partner Manager Service](https://docs.mosip.io/1.2.0/id-lifecycle-management/support-systems/partner-management-services) creates credentials for CA certificates to be used by [ID Authentication](https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-verification/id-authentication).
11. Printing Stage creates credentials for printing systems and sends the data through datashare.
12. [ID Repository](https://docs.mosip.io/1.2.0/id-lifecycle-management/identity-issuance/id-repository) Service sends data to ID Authentication system through Credential.