Settings & LLM Config
The Settings section of the NestFleet console is where Admins configure products, connect channels, tune triage behaviour, manage team members, and set up the LLM provider. Most settings are scoped to a specific product; some (like user management and system-wide LLM defaults) are global.
Only users with the Admin role can access Settings. Other roles can view their own profile and notification preferences but cannot modify product or system settings.
Product settings
Navigate to Settings → Products → [Product Name] → General to configure:
- Product name — displayed in the console header and in notifications
- Description — a brief description of the product passed to the triage agent as context. A clear, accurate description improves triage quality.
- Timezone — used for scheduled notifications (daily digest) and display of case timestamps
- Reply style — tone guidance for auto-reply generation (formal, casual, concise, detailed). This is injected into the auto-reply system prompt.
- Support email address — the inbound email address customers use to submit cases (if email is configured as a channel)
LLM provider setup
NestFleet supports per-product LLM configuration. The product-level settings override the system-wide defaults set via environment variables. This allows you to use different providers or models for different products (e.g. GPT-4o for your enterprise product, Claude Haiku for a high-volume free tier).
Navigate to Settings → Products → [Product Name] → LLM to configure:
- Provider — openai, anthropic, ollama, or google
- API key — stored encrypted at rest using AES-256-GCM (see ENCRYPTION_KEY)
- Model — the model name for standard tasks (auto-reply, knowledge capture)
- Fast model — override for triage and known-issue matching (optional)
- Complex model — override for change preparation and PR drafting (optional)
The API key field is disabled (read-only) after saving to prevent browser autofill from overwriting it accidentally. Click Change key to enter a new value. The stored value is never returned to the browser — the field shows only a masked placeholder.
Channel configuration
Channels are the inbound sources from which NestFleet receives cases. Configure them at Settings → Products → [Product Name] → Channels.
| Channel | What to configure |
|---|---|
| Inbound email address (or catch-all forwarding), SMTP backend (set globally via env vars). Specify which email domains to accept from. | |
| GitHub | Which repositories to listen to, the installed GitHub App, and which event types to ingest (issues, issue comments, pull request reviews). |
| Telegram | The Telegram bot token (set globally), and the specific Telegram group or channel to monitor for incoming user messages. |
| Webhook | A signed inbound webhook URL for custom integrations. Copy the secret and configure it in your sending system. |
Triage settings
Navigate to Settings → Products → [Product Name] → Triage to configure how the triage agent behaves for this product:
- Confidence threshold — the minimum confidence score (0.0–1.0) required for auto-reply to trigger. Default: 0.80. See AI Auto-Reply for guidance on tuning this.
- Auto-reply mode — Auto-send or Send for approval. Default: Send for approval.
- Severity policy — override the default P0/P1 escalation behaviour. For example, you can configure a product so that all
outage-type cases are always P0 regardless of confidence. - Novel bug threshold — the minimum knowledge-base similarity score below which a bug case is considered novel and a change request is automatically created. Default: 0.70.
- Auto-close spam — automatically close cases classified as
spamwith high confidence. Default: off.
Team members
Manage team members at Settings → Team Members. From this view, Admins can:
- Invite a new user — sends a one-time signup link by email
- Assign or change roles — select from the six built-in roles
- Deactivate a user — prevents login without deleting the account or audit history
- Reset a user's password — triggers a password reset email
See Roles & Permissions for a full description of what each role can do.
Billing
Self-hosted Community tier: NestFleet is free to self-host under AGPL-3.0 with no billing configuration required. The Settings → Billing section is visible but shows only a link to nestfleet.dev for information about paid license tiers that remove the "Powered by NestFleet" footer from auto-replies and unlock additional features.
If BILLING_ENABLED=true is set (SaaS deployments only), the Billing section provides Stripe subscription management. Self-hosted operators should leave BILLING_ENABLED=false.