Connections

Use the provisioned connection

Studio provides a Gnok connection for your organization. It uses your signed-in identity, so queries run with your own permissions. Existing connections and personal default selections are preserved.

Select a connection in the SQL editor's toolbar. Open Connections to inspect the profiles available to you and choose a default. An organization connection can be shared among members while queries continue to use each caller's permissions.

If no connection appears, refresh the connection list, then ask your administrator or email support@gnok.io. Do not enter another user's credentials.

Check the context

A profile can carry default catalog, schema, and warehouse settings, along with query limits and connection timeouts. Check these before running a saved query. A fully qualified name such as catalog.schema.table makes the target explicit.

A warehouse must be available to your account when required by the workload. A missing warehouse or table is not fixed by renaming a connection.

Additional connections

Use the connection form only when you have been given an additional supported endpoint and its authentication details. Follow the account's TLS and credential requirements. Personal and organization-visible connections have different audiences; choose the intended scope before saving.

Studio connection profiles are distinct from catalog registrations. A connection reaches a query service; a catalog describes data and metadata visible through that service.

Check that it works

Run SELECT 1 AS connected; in a new worksheet. If it succeeds but a table query fails, inspect the catalog/schema context and object privileges. If the connection itself fails, record the error and consult troubleshooting.

For external applications and BI tools, see client connectivity. Connecting from outside Studio isn't self-service yet; email support@gnok.io to set it up.