← All screens SIDEBAR · PROJECT

Settings combines connector health, capability models, knowledge sources and safe operational preferences.

Why it exists

Access

Model routing, RAG sources, workspaces and integration configuration require master authority. Operators can inspect health without seeing stored secrets.

Setting	Purpose
Fabric Intelligence AI provider and capability lanes	Choose an authoritative execution policy: Local only, Local + Cloud, or Cloud only. Local-only blocks cloud egress; cloud-only blocks generative Ollama fallback; hybrid lets Fabric Intelligence select governed capacity. Then configure Ollama, Anthropic/Claude or OpenAI/GPT and explicitly test it. In every policy Fabric Intelligence remains the intelligence layer—grounding, evidence, telemetry, approvals and learning stay active—and the local embedding index continues to power Fabric Intelligence Knowledge. Learning improves routing and approved context; it does not modify model weights. Read the complete routing, fallback, privacy and learning behavior. `FABRIC_AI_EXECUTION_POLICY` provides the startup default; `FABRIC_AI_EXECUTION_POLICY_LOCK=1` deliberately disables UI changes.
Workflow knowledge	Classify evidence as Shared/Common, Tech Art, Design, QA, Product, Production, Engineering/Code & data, or Operational so every workflow receives relevant context.
Custom sources	Add a local, web or gsheet source with provenance, label and collection. Index approved playbooks separately through Settings → Skills.
Operational connectors	Configure Jira, Perforce, Git, Sheets, Slack, Bugsnag, SmartBear MCP and native tools. Status and secrets remain separate.
Animated background and Fabric Pet	Device-local visual preferences; Pet messages reflect authoritative active work and rotate approval reminders without owning run state.
Time and cost estimates	Set manual/automated rates used by dashboard impact estimates; labels must distinguish estimates from measured values.
Logs	Search, copy and inspect bounded diagnostics. Clear the view only when appropriate; durable run evidence remains in its journal.

Never put passwords, API tokens, signing secrets or OAuth client secrets into source labels, logs, screenshots, agent JSON or RAG. Store them in the protected connector credential store and rotate anything exposed.