> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merchantops.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Lakehouse sharing

> Control whether your products, technologies, and MAP policies are shared across organizations.

MerchantOps keeps a shared **lakehouse** of reference data — product knowledge,
brand technologies, and MAP policies — that organizations can contribute to and
draw from. Lakehouse sharing settings let you decide what *your* organization
contributes to that shared pool. This page is for owners and admins; you need
settings permission to view these controls and edit them.

## What you control

There are three independent toggles, one per kind of contributed data:

<ResponseField name="Products" type="on by default">
  Whether the product knowledge your organization contributes (attributes,
  descriptions, and other enriched product data) is shared with other
  organizations or kept private to yours.
</ResponseField>

<ResponseField name="Technologies" type="on by default">
  Whether the brand technologies your organization contributes are shared or
  kept private.
</ResponseField>

<ResponseField name="MAP policies" type="off by default">
  Whether the [MAP policies](/pricing/map-policies) your organization
  contributes are shared or kept private.
</ResponseField>

## Defaults, and why they differ

**Products and technologies are shared by default.** This reference data
benefits every organization, so contributing it back is the default.

**MAP policy sharing is off by default.** A MAP policy is a legal agreement
between a specific brand and a specific reseller, so sharing it across
organizations carries legal and compliance risk. It stays private to your
organization unless you explicitly turn sharing on. See
[MAP policies](/pricing/map-policies) for how MAP data is governed.

<Note>
  Whatever you don't share stays fully usable *within* your own organization —
  turning a toggle off never hides your data from you. It only affects whether
  other organizations can see it.
</Note>

## Toggles affect future data only

This is the most important thing to understand about these settings:

<Warning>
  Changing a sharing toggle affects **future** contributions only. Data your
  organization has already contributed keeps the sharing decision it was saved
  with — flipping a toggle does not retroactively share or un-share existing
  records.
</Warning>

So if you turn MAP-policy sharing on today, only policies contributed *after*
that point are shared; earlier ones stay private. Likewise, turning a toggle off
doesn't pull back what you've already shared. If you need to change the sharing
state of existing data, treat it as a separate cleanup rather than expecting the
toggle to do it.

## Related

<CardGroup cols={2}>
  <Card title="MAP policies" icon="scale-balanced" href="/pricing/map-policies">
    How MAP policies are ingested, governed, and shared.
  </Card>

  <Card title="The lakehouse" icon="database" href="/data-ingestion/lakehouse">
    What the shared lakehouse is and how data gets into it.
  </Card>
</CardGroup>