LocoDELEGATIONS AI Connector – IT Guide
Download this guide: LocoDelegations-AI-Connector-IT-Guide-Short-v4.docx (Microsoft Word).
This concise guide is for council IT teams reviewing and setting up the LocoDELEGATIONS AI Connector during the beta programme.
What it is
The AI Connector lets an AI assistant your council already uses, such as Microsoft Copilot Studio or Claude, answer questions from your LocoDelegations data. A staff member signs in to LocoDelegations from inside the assistant, then asks questions in plain English. The assistant looks up the answer in LocoDelegations and replies. Administrators can also ask the assistant to make changes on their behalf. Everyone else has read-only access.
The facts IT teams ask about first
| Where it runs | Inside your council’s own LocoDelegations site, at the web address you already use. Nothing is installed or hosted anywhere new. |
| Who can use it | Only people who already have a LocoDelegations account. They sign in with the same login they use today, including Sign in with Microsoft where your council uses it, so your existing sign-in and multi-factor policies apply. There are no new accounts, passwords or shared keys. |
| What it can do | Anyone can ask questions and sees only what they could already see in LocoDelegations. Administrators can also make changes. Every request is checked against the person’s role, and every change is checked and recorded as if made in the browser. |
| Where the data goes | Answers go back to the AI assistant, so from that point they are covered by your council’s agreement with that AI provider (Microsoft, Anthropic or OpenAI). LocoDelegations never sends data to an AI provider on its own; the assistant has to ask, on behalf of a signed-in user. We recommend a business or enterprise plan where the provider does not train on your content. |
| Changes to your network | None. No new addresses, ports, certificates or firewall rules. If your council limits who can reach LocoDelegations by network address, the AI provider’s servers would need to be allowed. |
| Changes to Azure AD or Microsoft 365 | No new Entra app registration, API permission or tenant consent. Copilot Studio agents can be published centrally to selected users or groups through Microsoft 365. |
| Switching it off | Your LocoDelegations Administrator can remove any AI assistant’s access at any time from the AI Client Settings page. Locosoft can also switch the feature off for your council entirely. |
| Record keeping | Changes made through an assistant, and changes to which assistants are allowed, are written to the LocoDelegations change log. A log of each question asked is also planned for the beta. |
What works today, and what is coming
Today the connector does one thing: it confirms the connection works by reporting your council’s name, the signed-in user and their role. This lets you complete your security review and connect an assistant before any delegation data is reachable.
During the beta, for everyone: search delegations by keyword, act, role or position; list everything delegated to a role or position; show the delegations under an act or bylaw; show how a delegation has changed over time; and a log of each question asked. For Administrators only: making changes through an assistant, with the same checks as the LocoDelegations web pages and a change-log record for every change. Which changes are supported will be agreed with the councils taking part.
How sign-in works
- For Copilot Studio, IT publishes the configured agent centrally to selected users or groups through Microsoft 365, so staff do not add the connector themselves.
- On first use, the assistant asks the staff member to connect to LocoDelegations. For Entra councils this normally completes using their existing Microsoft sign-in; local-account councils sign in as usual.
- The connection is remembered. Access expires after one hour and renews quietly for up to fourteen days, after which the user signs in again.
Only assistants your Administrator has approved on the AI Client Settings page can start this process. Approving one takes a couple of minutes, as described below.
Connecting an assistant
Locosoft turns on the AI Client Settings page for your council when you join the beta. It is under Setup, visible to Administrators only, and shows the exact values for your site. In every case the address to give the assistant is https://<your LocoDelegations address>/mcp.
| Assistant | What to do |
|---|---|
| Microsoft Copilot Studio | 1. In Copilot Studio, open your agent, go to Tools, Add a tool, New tool, and choose Model Context Protocol. Enter the address above. 2. For authentication choose OAuth 2.0, then Manual. Copy the redirect URL it shows you. 3. In LocoDelegations, open Setup, AI Client Settings, Add a client. Give it a name, paste the redirect URL and click Add client. Copy the Client ID it generates. 4. Back in Copilot Studio enter that Client ID, leave the client secret blank, and use https://<your LocoDelegations address>/connect/authorize as the authorisation address, https://<your LocoDelegations address>/connect/token as the token and refresh address, and mcp email profile as the scopes. IT can then publish the agent centrally to the required users or groups; each user only connects to LocoDelegations on first use. |
| Claude (web, desktop, mobile) | 1. In Claude, open Settings, Connectors, Add custom connector. Enter a name and the address above. 2. Under Advanced settings, set OAuth Client ID to claude. Leave the secret blank. Click Add, then Connect, and sign in. |
| Claude Code (command line) | Run: claude mcp add –transport http locodelegations https://<your LocoDelegations address>/mcp –callback-port 33418 then /mcp to sign in. The port must be 33418. |
| ChatGPT | 1. In LocoDelegations, Add a client named ChatGPT with the redirect URI https://chatgpt.com/connector_platform_oauth_redirect and copy the Client ID. 2. In ChatGPT’s connector settings, create a custom connector with the address above, choose OAuth, paste the Client ID and leave the secret blank. OpenAI describes this redirect address as legacy, so ChatGPT may stop working without notice. Treat it as experimental during the beta. |
To test any of them, ask the assistant to “check my LocoDelegations connection”. It should reply with your council’s name, your name and your role.