---
title: Shared key value store
slug: optimizely-connect-platform/docs/shared-key-value-store-ocp2
docTags: 
createdAt: 2026-07-23T12:37:04.808Z
---

The App SDK provides a shared key value store instance available to all your application components. This store exposes the same [key value store interface](docId\:yZCeulHJFlZmUIxHo88wl) as the regular [key value store](docId\:wPncjf6QwaPMeEmbswmmx) and is intended as a way to share common data between different components of your application when the account isolation that the regular key value store provides is not necessary or is limiting.

A common problem this store solves is the persistence of mapping data between third-party systems, and Optimizely Connect Platform (OCP) accounts. For example, mapping source system account identifiers to OCP app install IDs. It is only required when a global function is included as part of the application, but its usage is not limited to this setup. For information on global functions, see [Global functions](docId:5qPanRhjTFsuT38y6Gy-G).

```typescript
import {storage} from '@zaiusinc/app-sdk';
await storage.sharedKvStore.put(sourceSystemId, zaiusInstallId);
```

:::hint{type="warning"}
**🚧 Important**
As a shared resource, take care with key namespacing to avoid key clobbering. Like the regular [key value store](docId\:wPncjf6QwaPMeEmbswmmx), do not write sensitive data such as API keys, API tokens, or usernames and passwords to the key value store. While the data is encrypted at rest, it does not have the same level of security as the [secrets](docId\:Fg0htEGqcx00Vcvflv-lB) or [settings](docId\:ASWmEhEHDdb_NVX3Fd9yV) stores and is not suitable for storing sensitive information.
:::
