Skip to main content

Who owns which class of record

GET 
/api/integrations/:provider/ownership

The answer to "does it make sense to hold the same record in two places". Decided per data class, not per feature — otherwise the argument restarts with every new screen.

null means nobody has decided, and an undecided domain behaves exactly as the product did before this setting existed. That is the only way a setting like this can ship to workspaces that already run.

Note what is NOT a domain: people. A contact is never mirrored beyond the link and the projection into empty fields, and the medical fields never enter the core at all. That is not a setting anybody gets to change.

Request​

Responses​

The map, with every domain listed even when unset.