Connecting an AI assistant
If you already use an AI assistant, you can connect it to your Provenience workspace and ask it about your projects and records. Administrators can also have it help with the Review Queue. Administrators and staff with an active Site login can approve and disconnect their own assistant connections in Provenience. Blue Data Works turns the connection on for your Site first, then gives you your Site's connection address.
Provenience follows the MCP authorization standard, so any assistant that can add a remote MCP server can connect. Claude and ChatGPT are examples. Some apps call this a "custom connector."
What it gives you
Ask your assistant things like "Which projects are open?", "Who is on the Smith job?", or "What did we record about the permit this week?" Answers come from the records Provenience has already organized. An administrator's answers include links into Provenience; staff answers identify records without Site links.
Your assistant never sees the original messages through this connection. It sees the organized records, project names, and rosters your account can read. An administrator's assistant also sees Review Queue cards; the administrator can open a source link to read the original text.
Your assistant acts as you, within your role's permissions (see below). The records it reads are shared with the assistant, under your own account with it, so connect it only where you are comfortable doing that.
One server, access by role
Your Site has one MCP server. It offers tools and instructions according to the caller's role. An administrator's assistant has the read, write, and proposal tools described on this page.
For a staff caller, the server offers only tools to read their projects, project rosters, categories, and records they are allowed to see. A staff assistant reads only what that staff member can see under their access rules. Their assistant cannot change records, propose changes, or see the Review Queue. Its answers contain record ids, without links into the Site or a Review Queue count. The company roster remains visible only to administrators.
Connect your assistant
Every assistant has its own screens, and they change, so yours may differ in small ways. The steps below are the ones they all share.
- Get your Site's connection address from Blue Data Works. It ends in
/mcp. If you have not been given one, the connection is not turned on for your Site yet. - In your assistant's settings, add a remote MCP server or custom connector. Paste the address and connect. If you do not see an option like this, ask whoever manages your assistant.
- Sign in to Provenience if you are asked to. You get a sign-in link by email, as usual. After you open it, you come back to the next step.
- Read the "Connect an app" screen. It shows:
- Name the app gave itself. This is the name the app chose, and Provenience has not checked it.
- After you answer, it sends you back to. This should be the web address of the assistant you are connecting, for example
claude.aifor Claude. This is the line to check. - Account. The account you are signing in as. The explanation below it describes what the app can do for your role: staff approve read-only access; administrators approve the administrator tools.
- Select Approve only if you just started connecting your assistant yourself, and the line above is the assistant's own web address. If you did not start this, or the address is one you do not recognize, select Deny. Both administrators and staff can approve their own connections.
- Back in your assistant, ask it to list your projects. If it names them, you are connected.
If the screen says the request has expired or was already answered, start connecting again from your assistant. If it keeps happening, tell Blue Data Works.
What an administrator's assistant can do
Your assistant can:
- Read your projects and their rosters, your categories, your records, and the Review Queue.
- Create a project, or rename one.
- Answer a Which project? or Which category? card, choosing from the projects and categories that already exist.
- Retry a message that could not be read.
- Exclude a card, or some of its texts, from the Review Queue.
The connection asks your assistant to confirm with you before it changes anything, but nothing in Provenience forces it to. Read what it says it is about to do before you agree. If it changes something without asking, stop it, tell Blue Data Works, and undo the change in Provenience if you need to. Changes it makes are recorded in your workspace's history with the name of the app that made them, the same way your own changes are.
What needs you in Provenience
An administrator's assistant cannot do these. It can ask for some of them, and it links you to where to do the rest:
- Access levels and access cards. Who can see what is decided in Provenience.
- New categories and other changes to your typology.
- Reprocessing a project.
- Accepting roster changes. Your assistant can propose adding or removing someone on a roster, adding a phone number, or registering an unknown number. A proposal changes nothing. It waits on the Proposals page until you accept or decline it.
- Renaming people, and deactivating phone numbers.
Why roster changes are proposals
Your assistant can use open Which project? cards to suggest roster additions. The cards show who was on each message; someone who recurs across cards about one job may belong on its roster. The assistant asks you to confirm before proposing the addition. Once you accept it in Provenience, the system reconsiders every earlier text that person was on. It can file texts that had no job yet and settle cards without another model call; it never takes a text off a job or changes a filing you made. See How records are filed, and what roster changes do.
Your roster decides who a text belongs to and who can see what. Someone who texts "add me to the Smith job" must never get onto a roster because an assistant read the message and acted on it. So your assistant can only ask. You see exactly what was asked, and you decide.
The note that comes with a proposal is the assistant's own wording and is shown as such. Check the values it proposes, not the note.
Waiting work
Every answer to an administrator ends with a count of the cards waiting in their Review Queue, and of proposals waiting for them. The assistant will usually mention them. They are your cue to open Provenience.
Disconnect your assistant
To disconnect, open Connected apps in Provenience and select Disconnect for the app. You can also remove the connection in your assistant.
Both administrators and staff see only their own connections. Staff land on Connected apps when they sign in to the Site.
Disconnecting means the app can no longer renew its access. Access it already holds stops within an hour. Revoking the person's Provenience access cuts off their assistant's access immediately.
Related
- Review Queue, the work your assistant can help with.
- Proposals, where roster and number changes wait for you.
- What Provenience can and cannot see.
- Govern and query the Catalog, for how access is decided.