Access Settings from the left sidebar by clicking Settings. The panel is divided into the following sections.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.
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.| 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 |
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.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.Features & Tools
Org-wide defaults and access controls for tools and features. Admins configure what’s available; users can adjust within those bounds from Personal. Default Chat Mode — Sets the default tools and connectors for all new chats across the org. Tool Access Control — Enable or disable specific capabilities org-wide:| Tool | Description |
|---|---|
| Web Search | Allow Ana to search the internet |
| SQL Execution | Allow Ana to write and run SQL |
| Ontology Access | Allow Ana to use the semantic layer |
| Ontology Editing | Allow users to edit the ontology |
| PowerBI Integration | Connect to Power BI datasets |
| Tableau Integration | Connect to Tableau collections |
| File Uploads | Allow users to upload files to chats |
| Multiple Connector Selection | Allow selecting more than one connector per chat |
| Chat History Search | Enable searching past chats |
| Environment Variables | Allow setting env vars in sandboxes |
| Enable Dashboards | Turn on the Dashboards feature |
| Model Switching | Let users switch AI models per chat |
| Observability | Enable query observability tools |
| Response Methodology Dropdown | Show methodology selector in chat |
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.