Data & Knowledge¶
View connector status and trigger a connector ingestion job. This page does not register new connectors or enter OAuth / database credentials.
| Console | Data & Knowledge |
| API | GET /v1/admin/connectors · POST /v1/admin/connectors |
| Mutating? | Trigger ingestion — yes (it_admin / app_owner) |
No credential setup here
POST /v1/admin/connectors starts an ingestion job ({accepted, job_id}). It is not a create-or-credential endpoint. First-time SharePoint, M365, Salesforce, SQL Account, AutoCount, or PostgreSQL setup requires Residion. See What still needs Residion.
Prerequisites¶
- At least one connector already configured on the appliance by Residion
- Mutating role to trigger ingestion; any role to view status
View connector status¶
- Open Data & Knowledge.
- Review each connector’s state, last sync, and RBAC labels (
GET /v1/admin/connectors).
Verify¶
- Status rows load for the connectors Residion configured.
- Hollow vs filled status marks (if shown) are informational only — interpret against the state field, not colour.
Trigger ingestion¶
- On Data & Knowledge, choose Trigger ingestion.
- Provide the connector and source ID required by the dialog.
- Submit. The API responds with
{accepted, job_id}on success.
Verify¶
- The console acknowledges acceptance and shows a job id.
- Re-check connector status / last sync after the job completes.
- Optional: confirm
POST /v1/admin/connectorsreturnedacceptedwith ajob_id.
If it fails¶
| Symptom | Likely cause | Action |
|---|---|---|
| 403 | auditor session |
Use it_admin / app_owner |
| No connectors listed | None configured yet | Contact Residion — credential setup is not self-serve |
| Looking for “Add connector” / OAuth fields | Not built for customers | See What still needs Residion |
| Job accepted but sync never updates | Upstream source or connector health | Re-check status; contact Residion with the job_id |