Security & Trust
Willow Boards holds a key to your ConnectWise instance. This page is written for whoever has to sign off on that: where your data sits, how those credentials are stored, how one workspace is kept away from another, and what our own staff can reach.
How your data moves
Willow Boards is a project layer, not a data warehouse. Your ConnectWise keeps the data. We store only the extra state that makes it easier to read, such as your board columns and dashboard layouts.
Authentication is handled by Microsoft Entra ID: your existing identity, your MFA and conditional-access policies. There are no Willow Boards passwords to manage or leak.
Every request runs inside your tenant's scope. Your projects, settings, and logs live in records partition-keyed to your workspace. Isolation is structural, not a filter.
Reads and writes go to your CW instance with your API member's permissions. Every write is filtered through a field allow-list and recorded in your audit log.
The pillars
Your ConnectWise API keys are held as per-workspace secrets in a dedicated, isolated vault: never in source code, never in the database alongside your data, and never sent to the browser. The application retrieves them using a platform-managed identity, so there is no vault password for anyone to store, share, or lose.
All workspace data, including project state, configuration, and logs, is partitioned by tenant at the database level, and every API request is bound to your tenant before any handler runs. Caches are tenant-keyed too, so one workspace can never serve another's data.
Four roles: Admin, Project Manager, Engineer, and Member. Each gates every write and sensitive read at the API, not just in the UI. Your admins see the full permission matrix in the app and assign roles per person.
Each change Willow Boards makes to your ConnectWise is recorded with who, when, from where, and what. Every write is filtered through a field allow-list, so only the fields you edited can change. The audit log is yours to review in the admin panel.
AI features are off until you enable them, and they're read-only. They summarize and advise, and they never write to ConnectWise. You connect your own agent or API key, so the model provider is your choice and nothing reaches it that you did not send.
The platform runs on major-provider enterprise cloud infrastructure, encrypted in transit (TLS) and at rest by default, behind hardened HTTP security headers and per-route rate limiting. Sign-in, data, and secrets all stay within that provider's cloud, and we run no servers of our own.
Shared responsibility
Some of this is ours to get right. The rest depends on how you configure your side, so it is worth knowing which is which.
| Willow Boards | You |
|---|---|
| Holds your CW credentials in an isolated vault and separates your workspace data | Create a dedicated CW API member with only the permissions you want Willow Boards to have. Least privilege is yours to set |
| Enforces roles on every API write and sensitive read | Assign roles to your team and review them as people change |
| Records every ConnectWise write in your audit log | Review the audit and API logs in the admin panel. They're built for your eyes, not just ours |
| Handles sign-in through Microsoft Entra ID | Your MFA and conditional-access policies apply automatically. Keep them on |
Common questions
Sent to us by vCISOs and IT directors reviewing Willow Boards. If yours isn't here, ask it.
Email [email protected]Workspace configuration, the project overlay state that powers boards and onboarding tracking, audit and error logs, and your account/team records. Project and ticket data itself lives in your ConnectWise. We read it on demand and write back only the edits you make.
No. Credentials are held in a dedicated vault, retrieved by the application itself at request time, and are never displayed back in the UI or sent to any browser. Operational access to production is restricted, least-privilege, and audited.
Your data is hosted on enterprise cloud infrastructure in the United States, encrypted in transit and at rest. Backups are continuous, with a 7-day point-in-time restore window, so we can roll the database back to any moment inside that window. We run in a single region to keep costs predictable. Reviewers who need the specific platform and region named can ask us directly.
Microsoft Azure (hosting, identity, data, secrets), Stripe (billing: card data never touches our servers), and Anthropic, used only where a workspace runs AI on our key instead of its own — with your own key, nothing reaches them. A current list is available on request.
A Data Processing Agreement is available on request. We are not yet SOC 2 certified; our controls are documented and we're happy to walk your security reviewer through the architecture on a call.
Workspace admins can remove members and configuration at any time; on account closure we delete your workspace data and destroy the vaulted secret holding your ConnectWise credentials.
Email [email protected]. We acknowledge reports promptly and will keep you informed through resolution.
Send it over. We'd rather answer your vCISO's hard questions before you connect your PSA than after.
Talk to us