-
Notifications
You must be signed in to change notification settings - Fork 7
Settings
Profile and System Settings are where you manage how Quickfire runs: billing linkage, user accounts, preferences, integrations, storage paths, templates, task masters, and diagnostics.
Quickfire intentionally separates responsibility across a few concepts so the system can scale without breaking itself later.
Users live locally inside Quickfire and control who can log in. Billing lives externally and gates access to advanced features without ever touching your data. Preferences are personal and only affect the current user. System settings apply agency-wide and shape shared behavior. Tasks define how renewals actually get executed in the real world.
That separation is what lets Quickfire run equally well as a solo desktop install or a multi-user server deployment without rewriting workflows.
Turning features on without touching your data
Billing controls user slots and access to premium integrations. It does not control, delete, or modify your data in any way.
To link billing, open Profile & Settings from the top-right user menu. The Billing Account card appears at the top of the page. Click Link Billing Account, enter your Quickfire billing email and password, and confirm the instance name if prompted. Once linked, the screen immediately updates to show billing status, available slots, and a Manage Billing button that opens the external billing portal.
If billing becomes inactive, your data remains intact and accessible. Premium integrations and advanced features are simply disabled until billing is restored. When something looks unavailable or a user cannot be added, checking billing status should always be your first step.
Personal identity, nothing more
The Profile section applies only to the currently logged-in user. From here you can update your name, email address, or reset your password. These changes do not affect permissions, workflows, visibility, or other users in the system.
Making the interface tolerable or powerful, depending on taste
Preferences are per-user and safe to experiment with. They control how the interface behaves rather than how data flows.
Audio can be disabled if notification sounds become distracting. Visual effects and animations can be reduced by turning off “Spicy Visuals,” which is useful on slower machines. Easy Mode (also called Safeties On) hides advanced and non-core controls, making it ideal for new hires, CSRs, or training environments. Daily Inspiration controls whether quotes appear on the Homepage and can be turned off entirely.
To change preferences, open Profile & Settings, navigate to Preferences, toggle the desired options, and close the page. Changes apply immediately without saving or reloading.
Who can log in, and why slots matter
The Users section manages local Quickfire accounts. These are the accounts that authenticate directly against your Quickfire database.
To add a user, go to Profile & Settings → Users, click Add User, enter the user’s name, email, and password, and assign a Desktop Username if you are running a desktop or tray-enabled build. The user becomes active immediately if a billing slot is available. If slots are exhausted, the user remains inactive until billing is adjusted.
The Desktop Username is critical in desktop deployments. It must exactly match the Windows login name for that user. This is what allows Quickfire to open files, interact with Word, and perform OS-level actions. If it does not match, those features will fail quietly by design.
Where operational discipline actually lives
Task Groups define what “done” means for a renewal. Every renewal is seeded from a Task Group, which means this section directly controls workload, timing, and accountability across your team.
When a renewal is created, its task list is generated from the selected Task Group. Goal dates are calculated automatically based on the policy expiration date, and those tasks flow straight into the Homepage priority list.
To edit or create a Task Group, open Profile & Settings → Tasks, select an existing group or create a new one, and begin defining tasks. Tasks appear in a hierarchy, with main tasks on the left and sub-tasks nested beneath them. Each task should include clear instructions, an optional default assignee, and a “Days Before Expiration” offset that defines when the task becomes due.
For example, a task called “Request Loss Runs” might be set to 100 days before expiration so it surfaces early enough to matter. Task Groups can be reordered using arrows for small changes or the Order tab for drag-and-drop reorganization. Groups can also be printed for internal review or training.
If renewals feel chaotic or deadlines are being missed, the problem is almost always here.
Emails that don’t embarrass you
Templates power Smart Email, Outreach, and automation-driven messaging. They are designed to reduce retyping while still enforcing context.
Templates are created and edited under Profile & Settings → Templates. When editing a template, you can include merge variables and optionally require a policy context. If a template references policy data, enabling the “Requires Policy Context” option prevents it from being used in the wrong place and sending partially populated emails.
Templates can be enabled or disabled without deleting them, which makes it easy to keep seasonal or specialized messaging on hand without cluttering day-to-day workflows.
One-click automation without magic
Custom User Agents are configurable automation actions that appear as buttons or AI-triggered workflows throughout the application.
To create one, navigate to Profile & Settings → Custom Agents and click New Agent. Each agent defines a name, icon, and outcome type such as a message, navigation action, download, or confirmation step. Agents can accept parameters like RenewalId or ClientId and can branch based on conditions.
Once created, agents can be placed into context-aware zones across the app so users can run actions without reselecting data they are already viewing. This keeps automation fast, visible, and auditable.
Wiring money into the workflow
The Payments section is where e-payment integrations are configured. After entering API credentials under Profile & Settings → Payments, Quickfire begins pulling recent payment activity and enabling paylink generation.
Once configured, payments surface naturally across the Homepage, Accounting views, and renewal workflows. Payment history becomes searchable and tied directly to the records that matter.
Persistent call history, not just popups
When telephony is enabled, the Calls section becomes your long-term call archive. From Profile & Settings → Calls, you can search and filter calls by phone number, directory, date range, text content, or recordings-only views.
Call data is stored locally, which means it remains searchable even if the external telephony API is temporarily unavailable.
Where external systems connect
The Sync section configures agency management systems such as Applied Epic or AMS 360. After selecting an integration, you enter API credentials, define folder mappings, and control how attachments and records are routed into Quickfire.
These settings determine how external data is normalized and where it lands, making them foundational to long-term data hygiene.
Agency-wide behavior
System Settings apply to everyone and shape shared behavior.
Agency information such as name, address, and time zone is configured here. The time zone setting is particularly important because it directly affects task deadlines, reminders, and date-based automation.
File storage is also configured at this level. Quickfire can store attachments locally, on a network share, or in cloud storage depending on the build. Changing storage modes does not migrate existing files automatically, so files must be moved manually when switching strategies.
The intelligence layer
Under the AI and Client Portal section, you configure your OpenAI API key and any client-facing portal connections. This enables AI summaries, SmartPaste, document extraction, and agent-driven workflows. Portal connections also power external update flows where clients can securely submit information back into Quickfire.
Teaching Quickfire where your mail lives
Email configuration lives under Profile & Settings → Email. Here you enter Microsoft Graph credentials, select which mailboxes Quickfire should monitor, and choose which provider is used for Blastmail sending.
These mailboxes feed Recent Emails, client activity timelines, AI summaries, and outreach history throughout the app.
DocuSign credentials are configured under Profile & Settings → Signatures. Once saved, signature workflows become available across renewals, proposals, and forms, and envelope history appears automatically on the Homepage.
Optional, but powerful
This section configures services such as Azure Document Intelligence and transcription providers. These tools are used by Proposler, SmartPaste, and AI-assisted document parsing to reduce manual data entry.
For power users and larger deployments
Depending on your deployment, this area exposes database engine selection, vector store configuration, and semantic mappings such as business glossaries. These settings directly affect AI search accuracy and natural-language query behavior.
When something smells off
The Logs tab is your primary troubleshooting surface. From Profile & Settings → Logs, you can review recent system activity, filter by log level, clear entries, or purge older logs. When support or diagnostics are needed, this is the authoritative source of truth.
Quickfire Wiki - Generated from Qf-Docs/wiki - Last updated: 2025-12-27.
See the main repo for README, issues, and release notes.
- Welcome
- Homepage
- Interface
- Profile & Settings
- Features
- Agents & AI
- Integrations
- Reference