Skip to content
Demiton

Connecting a System

Connecting a system gives Demiton access to that system’s data under your identity. The access profile varies by system - some connectors are read-only, others support governed writes. All credentials are encrypted at rest and every operation is fully audited.

To open Systems, go to Radial Menu → Wheel B → North (Systems), or press ⌘K and search for “Systems”.

The connection wizard

Demiton walks you through four steps. To start, click Connect a System on the Systems page.

  1. Select a system

    Browse or search for the system you want to connect. Systems are grouped by category - ERP, Payroll, Banking, Cognitive, Data Sources, and more.

    Click any system card to select it and advance to the next step. If a system shows a lock icon, it requires an access request before you can connect it - click the card to request access.

  2. Name and scope the connector

    Give the connector a name you’ll recognise later - for example, “Business Central Production” or “KeyPay AU”.

    Then choose an environment:

    EnvironmentUse for
    ProductionYour live system
    UATA staging or test instance

    The name and environment are displayed on the Systems page and used as the connector’s alias throughout the platform.

  3. Configure the connection

    Enter the credentials for your system. The fields vary by system type:

    Connection typeSystemsWhat you’ll need
    ODataBusiness Central, Finance & Operations, DataverseTenant ID, Client ID, Client Secret, and your base URL
    OAuth 2.0Xero, Azure AI FoundryClient ID and Client Secret - you’ll be redirected to the provider to authorise
    OpenAPI / API KeyKeyPay, Azure AI SearchYour API key and the base URL for your instance
    SFTPBanking GatewayHost, port, username, and an SSH key or password
    File uploadCSV / Excel data sourcesUpload a file directly - no ongoing connection required

    Before creating, click Test Connection to validate your credentials without committing anything. The test result will tell you exactly what failed if the connection can’t be established.

    Once the test passes, click Create Connector.

  4. Done - resources discovered

    The connector is live. Demiton runs a discovery pass and lists every resource the connection exposes - tables, endpoints, objects - so you can see exactly what data is available.

    From here you can:

    • Back to Systems - return to the Systems overview
    • Bind a Business Object - associate a business entity (e.g. a Worker or Project) with data from this connector

Adding a UAT/Production pair

If you connect the same system in both UAT and Production, Demiton links them as a variant pair - they appear grouped on the Systems page and share a logical alias so workflows can target either environment cleanly.

To add a variant:

  1. On the Systems page, find the existing connector
  2. Click Add Variant on its card
  3. The wizard opens at Step 2 with the environment pre-set to the opposite of what you already have
  4. Complete the credentials for the new environment

Platform-managed connectors

Some connectors - Azure AI Foundry, Azure AI Search, and Claude Enterprise - are configured and managed by Demiton on your behalf as part of your deployment. These appear in Systems but are not self-service. Contact your Customer Success Manager to enable or modify them.

After connecting

Once a connector is live, it is available for:

  • Workflow tasks - FETCH, PUSH, and EXECUTE verbs run against the connector’s resources
  • Studio - AI chat uses connected data as grounded sources for responses
  • Business Objects - bind entities like Workers, Projects, and Assets to data from the connector
  • MCP Server - your connected data becomes queryable via the Demiton MCP server

See the Connectors reference for system-specific credential guides.

Next steps