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.
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.
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.
Notifications — Control how you’re notified for Feed mentions and items shared with you. See 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
Ontology
Sharing
System Alerts
Developers
Manage programmatic access to the TextQL API. See 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 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 therefinery 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 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 for the full setup guide.
This section is hidden while you’re already inside the desktop app and for white-labeled organizations.
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
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 settings and its access to models is configured under Models. See Role-Based Access Control (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 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. Below that, Features lists every capability in your org on one page, organized into four groups. Available is the master switch — off means it’s gone for everyone; 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. Web Search, Ontology, and Observability additionally carry an Old/New mode selector next to their toggle.Agent Tools
Capabilities the agent uses to answer.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.
Visualization & Output
How answers get rendered, plus BI connections.Workspace & Access
Platform features and what members are allowed to do.Beta
Experimental features that may change or be removed — turning one on opts your whole org in.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.
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.
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 settings.
Models
Configure which AI models are available and how they’re accessed. See Model Management 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) 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 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.