Configuring Community Edition.
General setup: connecting your organization's entity and jurisdiction data (feeding Obligation Intelligence), setting up users and roles, and connecting your first integrations.
The three configuration surfaces
- Entities and jurisdictions
Your legal entities, sectors and member states — the facts Obligation Intelligence reasons over. Get these right and the applicability questions get answered; get them wrong and every downstream mapping inherits the error.
- Users and roles
Role-based access aligned to the same accountability model the platform preaches: named people, scoped permissions, no shared accounts. Administration is an audited activity, not a side channel.
- Integrations
Connector configuration for the tools you already run — read-only credentials, entity scoping, and sync settings per source, following the same model documented across the integration pages.
Configuration is data, not ceremony: declarative settings you can hold in version control, diff on upgrade, and restore on rebuild. The instance you run is reproducible — which is the whole point of self-hosting something inspectable.
From here, the one decision that shapes day-to-day operation is the AI inference source.
Configure your AI inference source