AI access
AI assistants such as Claude or ChatGPT get used anyway. So that nobody has to download participant lists and paste them into a chat, an assistant can connect to DELEGATOR directly. It then works with your account and may do exactly what you may. Personal data never reaches it.
Switching it on
AI access starts switched off for every conference. Project Management switches it on under AI access in the team area (group Maintenance), with Allow AI assistants for this conference. While the switch is off, no assistant sees anything of this conference, whoever connects it.
Once it is on, every member of the team may connect. The assistant acts with the roles of the person who connected it: someone who only holds Participant Care can do through the assistant only what Participant Care may. In a conference that is switched on, system administrators count as holding every team role. Their assistant reaches no further than the conferences that are switched on.
Connecting an assistant
Connect shows the address of the MCP server. Add it in your AI app as an MCP server (in Claude, for example, as a custom connector) and sign in with your DELEGATOR account in the window that follows. An assistant can then work with every conference that is switched on and whose team you are on. Ask it which ones those are first.
If the page says instead that no MCP server is set up yet, the server is missing its configuration. Contact the administrators.
What an assistant sees
An assistant reads the conference, committees, roles, delegations, applications, payment and document statuses, surveys, the schedule, papers and resolutions. It sees people only as ids with their status, roles and seats, whether they are minors, their school, city and country.
Everything else about people arrives as [redacted]:
- names, email addresses, phone numbers and addresses
- birthday, gender, pronouns and diet
- emergency contacts, access codes and invitation links
- every free text by or about people, such as care notes, motivation texts, sighting notes and comments on papers
When an assistant counts people by gender or diet, it leaves out groups of fewer than five and writes <5 there. It counts these two only alone or with each other, never together with a status, school, city, country, committee or role, since it knows those for every person.
An assistant cannot filter, sort or search by redacted details either. A question like "Who is called Miller?" is refused by DELEGATOR before it runs.
Working with ids
An assistant knows people only as ids and cannot tell you who is meant. Ask it for what it sees about a person, such as their delegation, role or school, and find them in the team area with that.
What an assistant can do
For common questions an assistant has tools of its own: an overview of the participants with their paperwork, counts by up to three attributes, and an overview of the assignment with seats, holders and warnings. Beyond that it can ask any read query the team area's pages use.
It can change what the team's pages change: committees, roles and seat planning, the assignment and sighting, the schedule, surveys, participant statuses, payments, the conference's settings and the tables' shared views. An assistant filters, sorts and groups a view only by columns without personal data, and saves no personal views. An assistant does not write notes or other texts about people. Those stay in the team area.
Preview first, then run
An assistant does not run right away what reaches people outside the team. That covers, for example, the conference stage, the conference information, unlocking payments, postal registration or paper submission, participant statuses and payments that trigger emails, and distributing a survey. The assistant first gets a preview and has to confirm the call explicitly. A good assistant asks you before it does. Only confirm what you would do yourself.
The log
Log lists every call an assistant made in this conference for someone on its team, the latest 200 first: when, by whom, which tool, with which Outcome (Done, Refused or Error) and with which details. Refused means DELEGATOR declined the call, for example because the assistant tried to filter by redacted details or the person's roles were not enough. When someone not on the team, or anyone while the switch is off, tries to reach the conference, DELEGATOR refuses without an entry here. Only Project Management sees the log.