Connections

Connections let Mind One communicate with external systems. Each connection defines the access credentials, the scope and the purpose of the integration.

Mind One will support different connection types depending on the purpose. Currently the available type is Autosync: automatic syncing of master data to an external storage system.

General concepts

Scope

A connection can be configured at two levels:

Workspace: all the workspace’s sheets automatically inherit the connection.
Sheet: the sheet has its own connection that overrides the workspace’s.

Workspace (default connection)
  └── Sheet A  →  inherits the workspace's
  └── Sheet B  →  inherits the workspace's
  └── Sheet C  →  has its own connection (overrides)

If a sheet has no connection of its own and the workspace doesn’t either, it doesn’t sync and its status stays as Skipped.

Status

Status	Description
Active	The connection is operational
Inactive	The connection is disabled
Error	The last operation failed

Management permissions

Only the Admin/Configurator roles can create, edit and manage connections. Other roles don’t have access to these options.

Testing a connection

Before enabling synchronization you can run a connection test to verify the credentials are correct without operating on the data.

Creating a connection

From the sidebar, go to Connections.
Click Create connection.
Fill in the name, an optional description, the platform type and the scope.
Enter the credentials specific to the selected type.
Click Test connection.
If the test succeeds, confirm the creation.

Governed connections in Mind Ocean

If your account has the Mind Ocean integration enabled, connections that are already governed there can be viewed inside Mind One without configuring them again.

The Connections list shows a Bring in Mind Ocean connections button (only if the integration is active for your account). Clicking it reflects Mind Ocean’s connections in the list, marked with a lock.

What you can do with them

They’re managed in Mind Ocean, so in Mind One they’re read-only: they can’t be edited, paused, deleted or tested, and they can’t be used as an Autosync destination either. Those action buttons appear disabled and explain why on hover.

What you can do is reference them from a sheet: a field validated against the Tenant Connections system list (tenant-connections) also offers Mind Ocean’s connections. Choosing one stores the identifier that connection has in Mind Ocean in the cell, so the sheet means the same thing on both sides — which is exactly what mapping sheets with a “Connection” column need, previously filled in by hand.

What you see for each one

Field	Content
Service	The service’s name exactly as Mind Ocean defines it — for example Qlik Cloud or Business Central
Mind Ocean Identifier	The id Mind Ocean uses for the connection
Service and Variant	How the connection is classified in Mind Ocean

No credentials are shown: the credential never leaves Mind Ocean. Mind One stores the reference, not the secret.

The integration is enabled per account and tied to the tenant’s Mind Ocean account: if that account is removed, the integration turns off — without it there’s nothing to sync against.

Autosync

Autosync is the feature that automatically syncs master data managed in Mind One with the customer’s lakehouse or external storage system. It uses the connection configured on the workspace or sheet to propagate changes to the destination in real time — no manual intervention, no periodic exports, no intermediate processes.

Sync status

Status	Description
Syncing	Sync in progress
Synced	Completed successfully
Skipped	No connection configured
Error	Failed — the error message is shown

Sync results

Each operation reports tables created and updated, records synced, per-record error details and the operation’s duration.

Autosync configuration by platform

Syncs Mind One’s master data with tables in Google BigQuery. Each sheet maps to a table within the configured dataset.

Required credentials:

Parameter	Description
Service Account JSON	The Google Cloud service account’s credentials file
Dataset ID	Identifier of the dataset where tables will be created
Data Location	Data location: `EU` or `US`

Configuration by scope:

At the workspace level, all sheets sync to the same dataset. At the sheet level, you can specify a different dataset.

Behavior:

If the table doesn’t exist in BigQuery, Mind One creates it automatically with the sheet’s schema.
If it already exists, it updates records via upsert by primary key or replaces the whole table, depending on the configuration.
The table name corresponds to the sheet’s Table Code.

Minimum Service Account permissions:

Permission	Purpose
`bigquery.datasets.get`	Verify the dataset exists
`bigquery.tables.get`	Read the structure of existing tables
`bigquery.tables.create`	Create new tables
`bigquery.tables.update`	Modify the schema of existing tables
`bigquery.tables.updateData`	Write and update records
`bigquery.tables.delete`	Delete tables if the sheet is deleted

The simplest option is to assign the predefined roles/bigquery.dataEditor role on the destination dataset.

Syncs master data with tables in Snowflake. Supports schema configuration per workspace or per sheet.

Required credentials:

Parameter	Description
Account	Account identifier (e.g. `xy12345.eu-west-1`)
User	User with write permissions
Password	The user’s password
Role	Snowflake role (e.g. `SYSADMIN`, `DATA_ENGINEER`)
Warehouse	Compute warehouse (e.g. `COMPUTE_WH`)
Database	Destination database

Configuration by scope:

At the workspace level, it defines the Snowflake schema where tables will be created.

Behavior:

Mind One creates the table if it doesn’t exist, with column types mapped from the sheet’s fields.
Changes sync via merge (upsert) using the unique field as the key.
The table name corresponds to the sheet’s Table Code.

Minimum role permissions:

Permission	Purpose
`USAGE` on the database	Access the database
`USAGE` on the schema	Access the destination schema
`CREATE TABLE` on the schema	Create new tables
`INSERT` on tables	Add records
`UPDATE` on tables	Modify existing records
`DELETE` on tables	Delete records
`MERGE` on tables	Upsert operations
`SELECT` on tables	Verify data status

Syncs master data with Delta tables in the Databricks Lakehouse via Unity Catalog.

Required credentials:

Parameter	Description
Workspace host	The workspace hostname without a protocol (e.g. `dbc-xxxx.cloud.databricks.com`)
SQL Warehouse HTTP Path	The SQL Warehouse’s HTTP path (e.g. `/sql/1.0/warehouses/xxxxxxxxxxxx`)
Access token	A Personal Access Token or Service Principal token
Catalog	The Unity Catalog catalog name (e.g. `main`, `prod`)
Schema	The schema name within the catalog (e.g. `default`, `mind_data`)

The Databricks connection uses HTTPS/TLS natively.

Configuration by scope:

At the workspace level, it defines the schema within the catalog.

Behavior:

Mind One writes to Delta tables within the configured catalog and schema.
If the table doesn’t exist, it’s created with the sheet’s schema.
Updates are done via Delta Lake’s MERGE INTO.
The table name corresponds to the sheet’s Table Code.

Minimum Service Principal or user permissions:

Permission	Purpose
`USE CATALOG` on the catalog	Access the destination catalog
`USE SCHEMA` on the schema	Access the destination schema
`CREATE TABLE` on the schema	Create new Delta tables
`MODIFY` on the schema	Insert, update and delete records
`SELECT` on the schema	Verify data status

Syncs master data with tables in Amazon Redshift. Supports both Redshift Serverless and provisioned clusters.

Required credentials:

Parameter	Description
Host	The Redshift cluster or workgroup endpoint
Port	Connection port (default `5439`)
Database	Destination database name
User	User with write permissions
Password	The user’s password
Schema	Destination schema within the database

Configuration by scope:

At the workspace level, all sheets sync to the same schema.

Behavior:

Mind One creates the table in Redshift if it doesn’t exist, with column types mapped from the sheet’s fields.
Updates are done via staging + merge to guarantee consistency.
The table name corresponds to the sheet’s Table Code.

Minimum user permissions:

Permission	Purpose
`USAGE` on the schema	Access the destination schema
`CREATE` on the schema	Create new tables
`INSERT` on tables	Add records
`UPDATE` on tables	Modify existing records
`DELETE` on tables	Delete records
`SELECT` on tables	Verify data status

-- Granting permissions in Redshift
GRANT USAGE ON SCHEMA mind_data TO mind_user;
GRANT CREATE ON SCHEMA mind_data TO mind_user;
GRANT INSERT, UPDATE, DELETE, SELECT ON ALL TABLES IN SCHEMA mind_data TO mind_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA mind_data
  GRANT INSERT, UPDATE, DELETE, SELECT ON TABLES TO mind_user;

Syncs master data with tables in a PostgreSQL database.

Required credentials:

Parameter	Description
Host	The PostgreSQL server’s hostname or IP
Port	Connection port (default `5432`)
Database	Destination database name
User	User with write permissions
Password	The user’s password
Schema	Destination schema (default `public`)
SSL	Enable an SSL connection (recommended in production)

Configuration by scope:

At the workspace level, all sheets sync to the same schema.

Behavior:

Mind One creates the table if it doesn’t exist, with column types mapped from the sheet’s fields.
Updates are done via INSERT ... ON CONFLICT DO UPDATE (PostgreSQL’s native upsert).
The table name corresponds to the sheet’s Table Code.

Minimum user permissions:

Permission	Purpose
`CONNECT` on the database	Establish a connection
`USAGE` on the schema	Access the destination schema
`CREATE` on the schema	Create new tables
`INSERT` on tables	Add records
`UPDATE` on tables	Modify existing records
`DELETE` on tables	Delete records
`SELECT` on tables	Verify data status

-- Granting permissions in PostgreSQL
GRANT CONNECT ON DATABASE my_database TO mind_user;
GRANT USAGE ON SCHEMA mind_data TO mind_user;
GRANT CREATE ON SCHEMA mind_data TO mind_user;
GRANT INSERT, UPDATE, DELETE, SELECT ON ALL TABLES IN SCHEMA mind_data TO mind_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA mind_data
  GRANT INSERT, UPDATE, DELETE, SELECT ON TABLES TO mind_user;

The Qlik Cloud connection syncs Mind One’s data directly to a Qlik Cloud space as a structured file. Mind One is the source of truth: data is maintained and governed in Mind One and synced to Qlik Cloud as files ready to be consumed by Qlik applications.

Required credentials:

Parameter	Description
Tenant URL	The Qlik Cloud tenant’s URL (e.g. `https://your-company.eu.qlikcloud.com`)
API Key	An API key generated from the Qlik Cloud Management Console
Space ID	Identifier of the space where files will be deposited

Export format:

Format	Description	When to use it
CSV	Comma-separated plain text	Maximum compatibility

Behavior:

Every time a change is saved or approved, Mind One generates the file in the configured format and deposits it in the Qlik Cloud space.
The file name corresponds to the sheet’s Table Code.
Qlik Sense applications can be configured to reload automatically when a new file is detected.

Required permissions:

Requirement	Description
Active API Key	Generated from Profile > API Keys in Qlik Cloud
Access to the space	The API Key’s owner must have the Can Edit role or higher on the destination space
Space type	The space must be of type Shared or Managed — personal spaces aren’t valid

No additional infrastructure permissions are required: an API Key with access to the space is enough.

Workspaces — Assign default connections to workspaces.
Sheets — Configure connections per sheet and check sync status.
Mind Ocean — Mind’s preconfigured data warehouse.

MCP Server

Connections

General concepts

Scope

Status

Management permissions

Testing a connection

Creating a connection

Governed connections in Mind Ocean

What you can do with them

What you see for each one

Autosync

Sync status

Sync results

Autosync configuration by platform

Related