Bodic Golden Source
One piece of data, one owner, one definition. Golden Source is your firm's shared reference: it catalogues your data, governs access by group, by user and by feature, and opens it to your AI assistants without ever handing over your systems.
The foundation everything else rests on
Every Bodic module reads from and writes to the same reference: funds, vehicles, holdings, accounts, contacts and indicators each have a single definition. That is what lets a figure published in an LP report be exactly the one the CRM displays, with no manual reconciliation and no argument about which version stands.
Golden Source is not one more database sitting alongside the others. It is the layer that gives every piece of data an owner, a definition and a trail.
What you own, written down somewhere
The catalogue lists the fund's reference data, its schemas, its owners and the business rules that apply to it. It is cross-cutting: it covers your whole information system, where the Portfolio Portal's Data Catalogue focuses on the data collected from your holdings.
- One owner per data set: who produces it, who validates it, and who answers when it is challenged.
- Schemas, types, units and nomenclatures documented in the same place as the data they describe.
- Business rules are written down rather than passed on verbally: thresholds, calculations, exceptions, edge cases.
- Every published value knows where it came from and when it was last validated.
By group, by user, by feature
Permissions are not a technical setting bolted on afterwards: they are part of the reference, and every module inherits them without ever redefining them.
By group
Build groups that follow your teams — investment, middle office, compliance, management — and grant them rights once and for all, rather than user by user.
By user
A named access can depart from its group, for the duration of an assignment or an audit. The exception is then explicit and dated, never implicit.
By feature
The permission covers what you do, not only what you see: view, update, delete and export are four distinct rights.
One set of permissions
What a user cannot see in the reference, they see in no module. There is no second set of access rights to maintain, and none to have audited.
Dashboards that rest on something
A dashboard is only worth its source. Multi-fund reporting consumes the reference rather than extracts: when a definition changes, it changes everywhere, and nobody compares two figures that never shared an origin.
- Indicators are defined once, in the catalogue, and reused as they are everywhere else.
- Governance follows: a dashboard never shows what its reader has no right to see.
- A figure's path stays readable, from the dashboard back to the data that produced it.
Your AI assistants read the source, on terms
Your teams already work with ChatGPT and Claude. The Bodic MCP server lets them query the CRM from those assistants, with no copy-pasting and without handing credentials to a third party. The point is not to expose your data: it is to frame that exposure.
Read-only, twenty-six bounded tools
Contacts, accounts, activities, funds, opportunities and pipeline are queried through twenty-six tools that can only read. Pagination, scopes and quotas by account type sit in the tool, not in the question.
The authorisation server is yours
It lives inside your CRM, hosted in France, and not at a foreign identity provider. You decide who authorises what, and that decision is kept with you.
Consent, revocable
The user authorises the application from a consent screen in the CRM, and withdraws that access whenever they choose under "Connected applications". No access installs itself quietly.
The assistant's token does not open the API
It is exchanged for a second token, with a distinct audience, before reaching your data. This is precisely the anti-pattern the MCP specification forbids: avoiding it is an architectural choice, not an implementation detail.
Two names in the log
Every call is logged with the user AND the application acting on their behalf. A question put to an assistant stays attributable, and can be found again.
Nothing leaves to train a model
The server answers reads; it feeds no training. Your data stays yours and stays in France, as with the rest of the platform.
What the reference feeds
Golden Source is not used on its own: it is the layer the other modules pass through.
Bodic CRM 360°
Accounts, contacts and activities draw their definitions from it. Explore Bodic CRM 360°
Bodic Business Intelligence
Dashboards consume the reference, not extracts. Explore Bodic Business Intelligence
Bodic Portfolio Portal
Holdings, their indicators and their campaigns. Explore Bodic Portfolio Portal
Bodic Data Room
Document permissions inherit the same groups. Explore Bodic Data Room
Bodic Golden Source
The reference
Bodic ESG & Impact
Fund aggregates build on the same reference data. Explore Bodic ESG & Impact
What our clients ask us
Do we have to migrate everything before we start?
No — quite the opposite. You begin by cataloguing what exists, flaws included: the reference data in place, its owners, its discrepancies. Convergence comes afterwards, module by module, at the pace of your own projects.
How is this different from an off-the-shelf data catalogue?
A generic catalogue describes data it does not govern. Here the definition, the owner and the access right live in the same place, and the modules apply them directly: there is no translation between what is documented and what is actually permitted.
Who can query the CRM from an AI assistant?
Only a user who has the right to, and only after explicitly authorising the application from their CRM. The assistant never holds more rights than the person it acts for, and that access is revoked in one click.
What exactly does the assistant see?
What the twenty-six read tools agree to return, within the user's own scope, with pagination and quotas. It does not reach the CRM API: the token it is handed does not open it.
Where is this data hosted?
In France, on Clever Cloud infrastructure, like the rest of the Bodic Apps. The authorisation server is hosted there too.
Let's talk about your reference data
In 30 minutes, let's look at what your firm calls "the right figure", and what it would take for it to be right everywhere.