Skip to main content

A hands-on workshop for workspace administrators: identity and SSO, roles and permissions, connector governance, capability and model controls, monitoring, and the day-to-day operations of running TextQL safely at scale.

It runs as short, hands-on modules with exact click-paths, copy-paste prompts, what you’ll see, and a checkpoint before moving on. Total time: about 2.5 hours.

​
What you’ll be able to do

Identity: SSO & SCIM

Login through your IdP; joiners and leavers handled automatically.

Roles & permissions

Least-privilege custom roles and the sharing model, demystified.

Connector governance

Who reaches which data, with which credentials, with what guardrails.

Capabilities & models

Org-wide tool toggles, model allowlists, limits, and spend.

Monitoring & audit

Audit log, thread-quality observability, and automated weekly review.

Governance operations

Patch review, access requests, on/offboarding, and the runbook.

​
Before you start

  1. You need the admin role — ideally in a staging org for Modules 1–2.
  2. Work through modules in order: identity → authorization → data → monitoring → operations.
  3. Steps give exact click-paths (e.g., Settings → Roles) or Prompts to ask Ana. Adapt anything in [brackets].
  4. Don’t skip Checkpoints — several settings have org-wide blast radius; checkpoints verify you haven’t locked anyone out.
Configuration details follow the current product docs at docs.textql.com. VPC / self-hosted deployments: substitute your own host wherever you see app.textql.com.

T-minus-1-day pre-flight: run the workshop’s key prompts end-to-end in the session workspace — confirm logins, connectors, and the features this workshop touches are enabled for every attendee; have a fallback demo workspace ready in case a customer connector fails live. Pacing: when a long prompt is running (2–4 min), fire it first, then discuss the concept while Ana works — never watch a spinner in silence. If behind schedule, cut sections marked optional, never the checkpoints. Group sessions: attendees drive, you narrate; collect every miss or wrong answer in a shared doc — that list is the ontology backlog. With 10+ attendees on one warehouse, stagger the heavy prompts.