Security and data for Kea and the Projectworks MCP
Who can use Projectworks AI, what it can see and change, how people sign in, and what happens to your data.
Overview
There are two ways to use AI with Projectworks:
- Kea is the AI built into Projectworks. It works in the Kea chat, in the Proposals editor, and in Expenses, where it reads receipts. There’s nothing to install, and no separate agent, service account or API key to manage.
- The Projectworks MCP connects Projectworks to an AI tool you already use, such as Claude, ChatGPT or Microsoft Copilot. Each person connects their own account.
Both act as the signed-in person, within that person’s existing Projectworks permissions.
Who can use it, and what can they see?
- Your Projectworks administrators decide who can use Kea and the MCP. They turn each one on for your account under ⚙️ Settings > Beta Features, then grant it through your existing access levels.
- Kea and the MCP see and change only what that person could in Projectworks. Dollar values stay hidden from people who aren’t allowed to see them.
- There are no shared or system-wide credentials.
- If a Claude Team or Enterprise admin adds Projectworks for their whole organisation, each person still needs the MCP turned on for their Projectworks account and allowed in their access level before they can connect.
Kea in Proposals comes with permission to edit proposals, with no separate switch. Kea in Expenses comes with the enhanced expenses beta, and works only on claims the person can create.
How do people sign in?
- The MCP uses OAuth 2.0 (authorisation code with PKCE) through the normal Projectworks login, so your SSO, including Microsoft Entra ID, and MFA apply.
- Each connection is tied to one person and one Projectworks account.
- Access tokens expire after 15 minutes.
Can AI change data without approval?
- Kea chat and the MCP: no. Every change is shown to the person as a plan first, and nothing is saved until they approve it.
- Plans can only be used once, belong to the person who made them, and expire.
- The person who asked for the change approves it. Normal Projectworks permissions limit what each person can change.
- Changes are saved all-or-nothing, so a failure doesn’t leave records half-updated.
- In Claude, you can also set each tool to always ask, always allow, or never run.
In Proposals, writing suggestions only go in when you accept them, and importing a proposal creates a new draft with the detected details filled in, which you can edit or remove.
In Expenses, scanning a receipt fills in a draft claim, and nothing is saved until you submit it. Your normal claim approval then applies.
Is there a record of what AI changed?
- Changes made through Kea or the MCP are recorded against the person who approved them.
- Resourcing changes, timesheet submissions and approvals, and leave status changes are also written to the change logs Projectworks keeps for those areas.
How do we remove access?
- People can disconnect AI tools themselves under Connected Apps in their Projectworks account settings.
- Deactivating a user in Projectworks stops their access immediately.
- Removing Kea or the MCP from an access level stops access, but can take up to 15 minutes.
- Include Projectworks in your leaver process. Disabling someone in Microsoft Entra ID alone doesn’t end a connection that’s already open.
Removing Kea from an access level doesn’t switch off Kea in Proposals. Remove permission to edit proposals instead.
Is our data used to train AI?
- No. Microsoft processes this data as a Projectworks sub-processor under the Microsoft Products and Services Data Protection Addendum. Under those terms, prompts and outputs aren’t used to train models and aren’t shared with OpenAI.
Where is our data stored and processed?
- Your Projectworks data, and anything Kea, Proposals and receipt scanning store, is kept in your hosting geography: Australia or Europe.
- Kea (including its help search), AI-powered Proposals and receipt scanning run on Microsoft Azure AI Foundry, using OpenAI models that Microsoft deploys and operates inside Projectworks’ own Azure subscription.
- Microsoft may process these AI requests in any Azure region where the model is available, under its Global deployment terms. This processing is transient, and the data isn’t stored outside your geography.
- Data shared with ChatGPT, Claude or another AI tool through the MCP is processed wherever your own account with that provider processes it.
- Proposal import (PDF and Word) is processed in Azure Australia Southeast, where all non-EU customers are hosted. It isn’t available yet for EU-hosted customers, and EU files are not sent to Australia.
Where are Kea conversations stored?
- In your own Projectworks database, visible only to the person who had the conversation.
- Microsoft Azure AI Foundry also keeps the conversation history.
What about MCP data in Claude, ChatGPT or Copilot?
Once Projectworks data is in your AI tool, that tool’s own terms and your own settings for it apply. The AI tool you choose is a separate supplier, under your own controls.
What about prompt injection?
- Kea treats page content and help articles as reference material, never as instructions.
- Approval is enforced by Projectworks’ servers, not just requested by the AI, so injected text can’t skip the approval step.
- Files uploaded to the Kea chat are scanned for malware by Microsoft Defender for Storage, and can’t be used until the scan finds no threats.
- Proposal imports accept only PDF, Word (.docx), Excel (.xls, .xlsx) and CSV files up to 10 MB, and images in the Proposals editor must be PNG, JPEG or SVG.
- With the MCP, how your AI tool handles content from other sources is controlled by that tool’s settings.
Can we keep our data separate?
- Each customer has its own database.
- MCP sign-ins are tied to a single Projectworks account and checked on every request.
Why use the MCP rather than the Projectworks API?
- API keys belong to your whole Projectworks account, not to a person, so API requests don’t follow individual people’s permissions.
- Changes made through the API are labelled “{Your company} API”, so you can’t tell which person made them.
- The MCP signs each person in with their own account, applies their permissions, and records changes against them.
Compliance
Projectworks holds SOC 2 Type 2. The report is available under NDA from our trust centre.
Recommended setup for regulated teams
- Grant Kea and the MCP only to the access levels that need them. Kea in Proposals follows permission to edit proposals, so check who has it.
- Start with questions before asking AI to make changes.
- In Claude, set the Projectworks tools that create or change records to ask before running.