Multi-Project Management

There is no hard cap on the number of projects per account. Create one project per client, environment, product line, or engagement as your organization requires. Most customers start with two or three and grow as they onboard new clients or separate staging from production. Projects are lightweight — creating a new one takes a click and does not require a new subscription.

Billing is unified at the account level. You pay once for your plan and the included assets and scans are shared across all projects in the account. This is deliberately designed for MSPs and enterprises — you never buy a separate subscription for each client or product line. Usage (assets, scans) rolls up to the account, while dashboards, findings, and access stay isolated per project.

Yes. Each project has its own asset inventory, findings, issues, scan schedules, and threat score. A user assigned to Project A cannot see Project B's assets or findings unless explicitly granted access. This is the standard model for MSPs managing multiple customers — the data separation is enforced at the query layer, not just hidden in the UI.

Yes. Owners and Admins get a cross-project overview on the main dashboard — aggregated threat levels, a comparison view of the riskiest projects, and one-click switching between them. Managers and Members only see the projects they are assigned to. This keeps operators focused while giving leadership and MSP principals the full picture.

Yes. Assets can be moved between projects without re-scanning from scratch — the scan history, findings, and issue state travel with the asset. This is useful when a staging asset graduates to production, when a client's scope changes, or when you restructure projects as your organization grows. The transfer is logged in the audit trail.

Yes. Each project has its own scan schedules, alert rules, and integration settings. One client might want weekly deep scans with Slack alerts; another might need daily light scans routed to email. Per-project settings also include color coding, naming, and default notification preferences — so the product adapts to each client's expectations instead of forcing one global configuration.

Yes — the multi-project model exists specifically for managed security providers and agencies. One FortWatch account holds every client engagement, each in its own isolated project, with per-project reporting you can deliver directly to the customer. Unified billing, shared admin team, isolated client data. It is one of the most common deployment patterns on the platform.

Enterprise customers typically create one project per product line, subsidiary, or region — keeping inventories and findings separate while retaining a single corporate security team that sees everything. This mirrors how internal audit and compliance functions operate: centralized oversight, decentralized execution. Cross-project reporting gives the CISO a portfolio view; per-project dashboards give each business unit ownership of their own surface.