System → Features is where you decide which modules your organization runs. AspirePro is deliberately modular: turn on what your team needs and leave the rest off, so the product stays focused and the sidebar stays clean.
Toggleable modules#
Each of these can be switched on or off independently:
- Dashboards & Reporting — shared dashboards and scheduled reports.
- Tickets — support queues, SLAs, email-to-ticket.
- Sales — pipelines and deals.
- Projects — project delivery and task management.
- Planners — flexible boards for any kind of work.
- Resource Management — capacity planning, staffing, time off.
- Finance — timesheets, agreements, invoicing.
- HR — people, performance, recruiting, assets.
- Notetaker — meeting recording and notes, powered by a notetaker service your organization connects (bring your own).
- Inventory & Purchasing — stock levels, purchase orders and receiving.
- Meeting Scheduler — bookable meeting pages.
- Knowledge — a permissioned knowledge base.
- Forms — capture the forms on your WordPress sites as contacts.
- Client Portal — a secure portal for your clients.
Switches inside a module#
Some modules have their own switches for parts of the module, shown on the module's card once it is on. For example, Dashboards & Reporting has Scheduled Reports (dashboards stay available without it), and Finance and HR have a switch for each area (Quotes, Invoices, Profitability, Directory & Org Chart, Training and so on). Turning one off hides that part and blocks its pages; existing data is kept.
Finance and HR also have Start from buttons that set the switches for you: for Finance, Everything, Quoting only, Billing and Reporting only; for HR, Everything, People only and People ops. Choosing one only sets the switches; nothing changes until you save.
AI#
The AI section has two organization-wide switches. Both are on to start with, and both take effect for everyone as soon as you save.
- AI features in AspirePro covers Prox, ticket AI (Detect tasks with AI and the Set priority with AI automation action), AI meeting notes, Read with AI on a consultant's invoice, Draft with AI on a project status report (a person checks it before the client sees it), and every other AI feature in AspirePro. They use our AI provider, xAI, which doesn't train on your data and, with Zero Data Retention, keeps nothing AspirePro sends it: each request is processed and discarded. While the switch is on, two of them run on their own: AI meeting notes and the Set priority with AI action. The rest run only when someone asks. Turn it off and nothing is sent: Prox and the AI buttons disappear, meeting notes aren't generated (Notetaker keeps the transcript), and automations skip their AI action while their other actions still run. Nothing is deleted.
- Connect AI clients (MCP) lets people connect their own AI app, such as Claude or ChatGPT, to AspirePro (see Developer & MCP access). Turn it off and every AI app connected to your organization is refused on its next request, with a message saying your organization has turned off AI client connections. New connections can't be made while it's off.
The two are independent. For example, you can stop AspirePro sending anything to xAI and still let people use their own Claude, or the other way round. Each change is recorded in the audit log.
Always-on foundations#
Some areas can't be turned off because everything builds on them. The Core card lists them: Dashboard, My company, Companies (including Lifecycle), Contacts and My work. These are always available regardless of which modules you enable. The one switch inside them is client health: scoring, and separately its notifications, can be turned off under System → Health scores rather than here.
Turning a module on or off#
- Open System → Features.
- Toggle the module.
When you enable a module, its navigation appears and its features become available. When you disable one:
- Its navigation is hidden and its routes are blocked, so no one can reach it.
- Its data is preserved — nothing is deleted. Turn the module back on and everything is exactly as you left it.
This makes it safe to experiment: enable a module to try it, disable it if the timing isn't right, and re-enable later without losing a thing.
Rolling out gradually#
A common approach is to start with the core modules your team will adopt first (say, Sales and Tickets), get those running well, then enable Projects, Finance, and the rest as you're ready. Because disabling is non-destructive, there's no penalty for phasing your rollout.
Enabling a module makes it available; it doesn't configure it. After turning one on, visit its settings to set up the statuses, boards, pipelines, or taxonomy it needs — see each module's documentation.