Application Settings
These pages are Endatix API settings: the Endatix object in appsettings.json (or environment variables bound the ASP.NET Core way). Per-environment files work like appsettings.Production.json.
Endatix settings live in three places. Use the matching docs so operators do not hunt in the wrong file.
| Layer | Where | Who | Docs |
|---|---|---|---|
| API host | appsettings.json / API env (Endatix:*) | Developers / host operators | This Settings section |
| Hub host | Hub .env / Helm (ENDATIX_*, AUTH_*, STORAGE_*) | Developers / host operators | Hub environment variables |
| Hub UI (audit) | Platform Admin pages | Platform administrators | Email Settings, Environment, Auth Settings |
Hub does not read appsettings.json. The API Hub URL page is only how the API builds links to Hub (emails and exports).
{
"ConnectionStrings": {},
"Endatix": {
"Data": {},
"Auth": {},
"Cors": {}
}
}
Shipped samples live in src/Endatix.WebHost (appsettings.json, appsettings.Development.json). Keep production secrets out of git.
Auth Settings
These are Endatix API JWT settings (Endatix:Auth). They sign tokens the API issues.
CORS Settings
These are Endatix API settings (Endatix:Cors). Hub origin for Auth.js is AUTH_URL — see Hub environment variables.
Data Settings
These are Endatix API settings (Endatix:Data). They control migrations and sample seeding.
Email Settings
Configure email providers, identity email templates, and sender addresses in the Endatix API.
Health Checks
These are Endatix API health-check settings. Hub has its own maintenance and telemetry env — see Hub environment variables.
API Hub URL
Point the Endatix API at your Hub origin so emails and exported file links open the right UI.
Persistence Settings
These are Endatix API settings (Endatix:Persistence). They pick the database provider, connection strings, and migration behavior.
Storage Settings
Configure Endatix external file storage - Azure Blob Storage and S3-compatible services — with all supported settings and environment variables.