> ## Documentation Index
> Fetch the complete documentation index at: https://docs.textql.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Settings Overview

> A guide to every section in the TextQL Settings panel

Access Settings from the left sidebar by clicking **Settings**. The panel is divided into the following sections.

<Note>Some sections may not be visible depending on your role. If you need access to a setting that isn't shown, reach out to your organization's admin.</Note>

## Personal

Your individual profile and defaults — changes here only affect your account, not the whole org.

**Profile** — Update your display name and profile picture.

**My Chat Defaults** — Set which tools and connectors are pre-selected when you open a new chat.

| Tool | What it does |
| - | - |
| Web Search | Lets Ana search the internet |
| Text to SQL | Lets Ana query your databases |
| JavaScript | Lets Ana run JavaScript for visualizations |
| Bash | Lets Ana run shell commands |
| Ontology | Lets Ana use your semantic ontology layer |

You can also select which connectors are checked by default. Use **Reset to org defaults** to revert to whatever the admin has set in [Capabilities](#capabilities).

**Notifications** — Control how you're notified for Feed mentions and items shared with you. See [Notifications](#notifications) below for full details.

## Notifications

The **Notifications** tab lets you control how and where you receive alerts from TextQL. Access it from **Settings → Notifications**.

Each notification type can be delivered via **In-App**, **Email**, or **Slack** (Slack requires the Slack integration to be connected).

### Feed

| Event | Description |
| - | - |
| **Mentions** | Notified when you're @mentioned in a post or comment |

### Ontology

| Event | Description |
| - | - |
| **Sync failures** | Notified when an Ontology git sync fails with error details |
| **Patch submitted** | Notified when an Ontology patch is opened for review |
| **Patch approved** | Notified when your Ontology patch is approved |
| **Patch denied** | Notified when your Ontology patch is denied |

### Sharing

| Event | Description |
| - | - |
| **Shared with you** | Notified when someone shares a thread, playbook, agent, or dashboard with you |
| **Access requested** | Notified when someone requests access to content you own |
| **Access approved** | Notified when your access request is approved |
| **Access denied** | Notified when your access request is denied |

### System Alerts

| Event | Description |
| - | - |
| **Alerts & broadcasts** | Important system alerts and announcements from your organization |

## Developers

Manage programmatic access to the TextQL API. See [Embedding Ana](/core/guides/embedding-ana) for how to use these keys.

**API Keys tab** — View all API keys in the org (filterable by owner and status). Click **+ Create API Key** to generate a new key with optional name, expiry, and role scoping. Admins can revoke any key. See [API Keys](/core/admin/api-keys) for full details.

**Service Accounts tab** — Create bot identities with fixed roles for production use cases (embeds, automations). Unlike personal keys, service account keys survive employee turnover and have immutable roles. Generate keys from the **Service Account Keys** tab or the service account's **Create API Key** action.

## Desktop & CLI

Download the native desktop app and the `refinery` CLI.

**Desktop app** — Auto-detects your OS and highlights the right build (macOS, Windows, or Linux); every other platform's installer is listed below it. See [Desktop App](/core/integrations/desktop-app) for details.

**CLI** — Auto-detects your OS and architecture (including Apple Silicon vs. Intel) and gives you a one-line install-and-login command, plus a ready-made prompt you can hand to a coding agent to install and configure `refinery` itself. See [CLI](/core/admin/cli) for the full setup guide.

<Note>
  This section is hidden while you're already inside the desktop app and for white-labeled organizations.
</Note>

## Members

View and manage everyone in your organization. Admins can:

* **Invite Member** — Send an email invite to add someone to the org
* **Assign Roles** — Bulk-assign roles to members
* Search and filter members by role
* Use the `⋮` menu on any row to manage or remove a member

See [Role-Based Access Control (RBAC)](/core/admin/rbac) for how roles work.

## Roles

Create and manage roles for access control. TextQL has two system roles (**admin** and **member**) and supports unlimited custom roles.

Custom roles let you scope which connectors, context files, and tools specific users can access. Once a role is created, its permissions are set in the [RBAC](/core/admin/rbac) settings and its access to models is configured under [Models](#models).

See [Role-Based Access Control (RBAC)](/core/admin/rbac) for full details.

## Notification Overrides

Admin-only. Force the organization's choice for a specific notification rule instead of leaving it to each member's own [Notifications](#notifications) settings.

Toggle **Override** on for a rule to apply the org's In-App/Email choice to every member — their own setting for that rule becomes read-only. Toggle it off to hand control back to members; nothing is copied onto their preferences, so an un-overridden rule is entirely theirs to decide.

## Appearance

Customize the look and feel for your organization.

**Customize Organization Theme** — Upload or remove your organization's logo. The name shown here is your org name.

**Customize Playbook Theme** — Open the Theme Editor to configure colors, backgrounds, and styling for reports and playbook outputs.

## Capabilities

**Thread Default Connectors** sits at the top of the page — a searchable, checkable list of every connector in your org, showing which ones are switched on in every new thread. Checking or unchecking one here only changes its default state for new threads; to add, remove, or configure a connector itself, use the [Connectors page](/core/datasources/the-connectors-page).

Below that, **Features** lists every capability in your org on one page, organized into four groups. **Available** controls whether the corresponding tool or feature can be used across the organization; **Default** is whether an available capability starts active in a new thread. Related settings nest under their parent, and Slack threads are unaffected. Admins configure what's available; users can adjust within those bounds from [Personal](#personal). Observability carries an Old/New mode selector next to its toggle. Ontology shows that selector until your organization switches to Ontology 3.0. After the switch, Ontology's **Available** toggle controls `.tql` queries, not access to the Ontology library.

### Agent Tools

Capabilities the agent uses to answer.

| Tool | Description |
| - | - |
| Web Search | Searches the live web for current information and cites its sources |
| SQL | Writes and runs SQL against your databases to answer questions |
| Ontology | Lets the agent answer through your ontology instead of raw tables |
| ↳ Ontology queries | Legacy Ontology only: whether new threads start with ontology queries on |
| Email | Lets the agent send email to members of your organization |
| Bash | Lets the agent run bash scripts in a sandboxed environment |

<Note>
  Organizations still on the legacy Ontology mode see an Ontology queries default plus sub-settings for editing the ontology from threads, auto-approving edits, and context.
  In the new ontology, these are replaced by TQL queries, which are always enabled unless the org explicitly forbids this tool.
</Note>

### Visualization & Output

How answers get rendered, plus BI connections.

| Setting | Description |
| - | - |
| Dashboards | Builds interactive, shareable dashboards from a thread's results |
| ↳ Default to dashboard output | Turns on dashboard as an output format by default in new threads |
| JavaScript Visualizations | Custom JS-rendered charts — retired automatically once Data Apps is enabled |
| PowerBI Integration | Connects to Power BI and queries its datasets |
| Tableau Integration | Connects to Tableau and queries its workbooks |
| Emojis | Lets the agent use emoji in its responses. Off by default |
| [Response Methodology](#response-methodology) | Adds a per-chat dropdown to pick how thorough vs. fast and cautious replies are |
| ↳ Default methodology | The methodology new chats start with; members can override it from the chat composer or their personal settings |

### Workspace & Access

Platform features and what members are allowed to do.

| Setting | Description |
| - | - |
| File Uploads | Lets users attach files for analysis in a thread |
| Thread History Search | Searches past threads for relevant context |
| Environment Variables | Stores credentials the agent can use to call external services |
| Sharing | Lets users share threads, playbooks, connectors, and other objects with members of the org |
| Model Switching | Lets users pick the model per thread, within admin-set limits |
| Citations | Adds inline source citations to agent answers so claims link back to the cells that produced them |
| API Connectors | Connects external web APIs the agent can call from its sandbox |

### Beta

Experimental features that may change or be removed — turning one on opts your whole org in.

| Setting | Description |
| - | - |
| [Data Apps](/core/how-it-works/data-apps) | Builds interactive, generative Data Apps from a thread's results |
| Feed and Agents | A shared insights feed, and autonomous agents that post to it |
| [Subagents](/core/how-it-works/ana/subagents) | Lets the agent delegate focused sub-tasks to child agents |
| [Voice Input](/core/how-it-works/tools/voice-input) | Adds a microphone to the chat composer for dictating prompts. Requires a transcription provider configured on the deployment |
| Observability | Gives admins a birds-eye view of agent and user activity, plus quality checks |
| Notifications | Enables the in-product Notifications hub for your org |
| [Training Mode](#training-mode) | Makes the agent ask clarifying questions and avoid assumptions. On by default |
| Example Connectors | Adds demo data sources for onboarding and testing |
| Fast Mode | Faster inference for supported models, at higher cost |
| Max Thinking | Extended thinking at maximum effort for supported models |
| Parallel Tools | Runs independent tool calls at the same time |
| Sandcastles | Adds a Sandcastles section under Observability for inspecting running sandcastles and their files |
| ↳ Configurable Sandcastles | Sets how long a sandcastle stays alive after its last activity, per class (threads, dashboards) |
| Forms | Lets the agent draft and pre-fill forms (e.g. connector setup) in a thread |
| Question Tool | Lets the agent pause and ask you structured questions inline in a thread |

### Behavior Settings

Training Mode, Emojis, and Response Methodology shape *how* the agent reasons and responds, rather than what it can access. They're layered onto the agent's system prompt at the start of a conversation, are provider-agnostic — the same behavior whether a chat runs on Claude, GPT, Gemini, or Kimi — and switching models mid-conversation doesn't change which behaviors are active.

#### Training Mode

Makes the agent ask clarifying questions and avoid assumptions.

| Training Mode | Behavior |
| - | - |
| On (default) | The agent flags missing context, surfaces its assumptions, and asks clarifying questions before answering |
| Off | The agent answers directly, inferring intent from the request without pausing to confirm |

Useful when onboarding new users, when data models are unfamiliar, or for high-stakes analysis where a wrong assumption is costly — it trades a small amount of speed for fewer misdirected answers.

#### Response Methodology

Adds a per-chat dropdown letting users pick how thorough versus fast and cautious the agent's replies are. When disabled, the dropdown is hidden and every chat runs on the org's default methodology.

| Methodology | Behavior |
| - | - |
| Adaptive | The agent judges per request how much depth and clarification each task needs |
| Prescriptive | The agent moves quickly and decisively, making reasonable assumptions to deliver a direct answer |
| Thorough | The agent prioritizes depth and completeness over speed |
| Careful | The agent minimizes assumptions and asks clarifying questions before acting |
| Ontology Building | Available on Ontology 3.0 only; the agent works with you to build and refine the semantic layer as it answers |

The **Default methodology** sub-setting (in the table above, nested under Response Methodology) sets which of these new chats start on — members can still override it from the chat composer or their own [Personal](#personal) settings.

## Models

Configure which AI models are available and how they're accessed. See [Model Management](/core/admin/models) for full details.

The **Models** tab has three sub-tabs:

**Model Catalog** — Set the org-wide default model (shown to users as "Default" in the chat picker). Enable or disable individual models, view ACU pricing per 1M tokens, and browse available providers (Anthropic, OpenAI, Fireworks).

**Role Access** — Restrict which models specific roles can use. Useful for cost control — you can lock non-admin roles to cheaper models.

**Analytics** — View model usage across your org.

## Security

Controls for user access, identity, and workspace configuration.

**Allowed Email Domains** — Only users with matching email domains can join the org. Toggle **Workspace Discoverable by Domain** to let matching users self-join without an invite.

**OIDC Identity Providers** — Configure SSO via Okta, Azure AD, Ping Identity, or any OIDC-compliant provider. See [Single Sign-On (SSO)](/core/admin/sso) for setup guides.

**SCIM Provisioning** — Automate user and group sync from your identity provider using the SCIM 2.0 endpoint (`https://app.textql.com/scim/v2`). Generate Bearer tokens or create OAuth 2.0 clients here. See [SCIM Provisioning](/core/admin/scim) for details.

**Create Sibling Workspace** — Spin up a new workspace that shares the same billing tenant and inherits your org's identity providers and allowed email domains.

**Workspace Retention** — How long thread sandbox state is preserved after last activity (default: 30 days). Active threads are never affected.

**Delete Organization** — Permanently deletes the org and all associated data. Irreversible.

## Packages

Install custom Python packages that become available in all Ana sandboxes across your org. Useful for domain-specific libraries (e.g., finance, PDF parsing, NLP).

Click **+ Install Package**, enter the package name and version, and it will be installed and listed here. Installed packages are available immediately in new Python cells.

## Audit Log

A tamper-evident log of security and administrative actions across the org. See [Audit Log](/core/admin/audit-log) for full details.

Filterable by category (Settings, RBAC, Auth, etc.), action type, and time range. Useful for compliance reviews and investigating access incidents.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.