Skip to content
AgentZforiMIS®

Glossary

The terms used in AgentZ and in this documentation, in alphabetical order, each with the name you see on screen and the article that covers it. Other pages link a term here the first time they use it.

The Activity page in the AgentZ app lists your agents and every step each one has taken, with its result. It is kept on your computer. It is not the Team changes record on the Team tab. See Activity and approvals.

See Organisation admin.

One conversation in your AI app that is doing work in iMIS through AgentZ. You can run several agents at once; the Activity page lists each one by name. See Activity and approvals.

iFINITY’s product for doing work in iMIS through an AI app. It has three parts: the AgentZ app on your computer, the AgentZ plugin in your AI app, and the AgentZ service that holds your licence. See Overview of how AgentZ works.

The app you install on your Windows PC or Mac. It signs you in to AgentZ and to iMIS, opens iMIS in its own iMIS browser, connects your AI app, and shows what each agent is doing. Windows and macOS list it as iFINITY AgentZ. See The AgentZ app.

Your organisation’s colours, fonts and design rules, which agents follow when they build pages, dashboards and themes in iMIS. You see and change it on the Design tab of Tools. It holds one or more design sets. See AgentZ Design.

The part of AgentZ that runs inside your AI app and gives it the steps it can take in iMIS. The AgentZ app adds it to each AI app and keeps it up to date. See The AgentZ plugin.

iFINITY’s online service at ifinityagentz.co.uk. It holds your organisation’s licence and seats, signs you in to AgentZ, keeps your team’s shared records, and gives the AgentZ app its iMIS access token. See What iFINITY receives.

The app you talk to, such as the Claude desktop app, Claude Code or Codex. AgentZ works inside it through the AgentZ plugin. The AI apps tab in Settings shows each AI app on your computer. See Working with your AI app.

To allow a change before AgentZ makes it. AgentZ shows a preview of the change, waits for you to approve it in your AI app or the AgentZ app, then reads the result back from iMIS. See How work is shown and approved.

The code iFINITY gives your organisation to activate AgentZ. Your Organisation admin enters it after choosing Use your auth code on the AgentZ app’s sign-in screen. It also unlocks the downloads on ifinityagentz.co.uk. See Signing in to AgentZ.

Work that carries on after your AI app has moved on, such as installing a BuildHub app. You follow it in the AgentZ app, and AgentZ picks it up again if it was interrupted. See Installing a BuildHub package.

The catalogue of ready-made iMIS work, such as BuildHub apps and configuration packages, that you can install on your iMIS site from the BuildHub tab of Tools. See BuildHub.

The record in iMIS, under Settings > Contacts > Client applications, that lets AgentZ use the iMIS API. AgentZ creates it when your Organisation admin sets up the iMIS API connection. See Setting up the iMIS API connection.

A set of iMIS items, such as queries, pages, layouts, forms, business objects and panels, with what they depend on, that AgentZ moves from one iMIS site to another. See BuildHub.

One named set of colours, fonts and rules in AgentZ Design. A website or a sub-brand can have its own design set. See AgentZ Design.

See iMIS site for the iMIS your organisation uses, and Work area for a group of recipes.

The staff page for one event in iMIS. AgentZ can add a panel to every event’s console. See What AgentZ can do in iMIS.

A short-lived pass that lets AgentZ use the iMIS API as you. The AgentZ app gets it from iMIS and renews it with a renewal token. See iMIS access tokens.

What lets AgentZ read and change records in iMIS through the iMIS API, as you. Your Organisation admin sets it up once for each iMIS site, on the iMIS tab in Settings, unless the Team tab lets team members do it too. It also needs a system administrator in iMIS. See Setting up the iMIS API connection.

The browser inside the AgentZ app where iMIS opens. You and your agents use it in turn: you can take it over from an agent and hand it back. See The iMIS browser.

ASI’s cloud version of iMIS. See AgentZ requirements.

Your iMIS staff username and password, saved in the AgentZ app so it can sign you in to your iMIS site. You enter them on the iMIS tab in Settings, never on a web page. See Connecting your iMIS site.

The iMIS your organisation uses, at its own address, such as yourorg.imiscloud.com. It holds your records and your websites. If you work with more than one, the iMIS sites tab in Settings lists them. See Connecting your iMIS site and Adding another iMIS site.

Your organisation’s right to use AgentZ, held by the AgentZ service. It sets how many seats your organisation has. See Seats and team members.

The website in your iMIS site that AgentZ treats as your main public one, chosen on the iMIS tab in Settings. See Choosing your main website.

The Organisation admin named on your organisation’s licence. The Team tab marks them Main contact. See Seats and team members.

A person who manages AgentZ for your organisation: they see the Team tab, remove people, sign people out and set team permissions. See Seats and team members.

What AgentZ shows you before it makes a change: what will change, where, and what stays as it is. See How work is shown and approved.

A ready-made request for a common job in iMIS, which you copy into your AI app. Recipes are grouped by work area. See Recipes.

What the AgentZ app uses to get a new iMIS access token when the last one ends, without asking you to sign in again. See iMIS access tokens.

What you ask your AI app to do, such as “Find members whose membership ends this month”. Each request becomes one or more steps. See Making your first request.

One person’s place in your organisation’s licence. You take a seat when you first sign in to AgentZ, and an Organisation admin can free it. See Seats and team members.

The AgentZ app’s screen for setting it up, opened from the lower-left of the window. Its tabs are Overview, iMIS sites (when you have more than one), iMIS, AgentZ, AI apps and Team (for Organisation admins). See Overview settings.

The Setup button in the sidebar. It opens the Overview tab of Settings, which lists each part of setting up AgentZ and the one thing to do next. See Checking your setup.

The link AgentZ emails to your work address when you sign in to AgentZ. Opening it signs in the AgentZ app. See Signing in to AgentZ.

One thing an agent does in iMIS through AgentZ, such as running a query or saving a page. The Activity page lists each step, and you can stop one with Cancel this step. See Activity and approvals.

The iMIS role, set in iMIS, that can manage its settings and Client Applications. It is separate from being an Organisation admin in AgentZ.

To use the iMIS browser yourself while an agent is working in it. Take over the browser gives it to you, and Hand back the browser gives it back to the agent. See Taking over from an agent.

The Team tab in Settings, shown only to Organisation admins: who holds a seat, how much each person uses AgentZ, their devices, team permissions, and how long iFINITY keeps your organisation’s records. See Seats and team members.

The record of changes to your team, such as who was added, removed or signed out, kept by the AgentZ service. Organisation admins choose how long it is kept, on the Team tab. It is not the Activity page. See Seats and team members.

A person with a seat who is not an Organisation admin.

Outcomes and decisions people have shared with the rest of the team from their agents’ work, kept by the AgentZ service. See Sharing across your organisation.

What an AI app calls each kind of step AgentZ offers it. Your AI app may ask you to allow a tool the first time an agent uses it. In the AgentZ app, Tools is the screen with Design, Migration and BuildHub. See Working with your AI app and AgentZ Design.

A website built in your iMIS site with RiSE, such as the staff site or a member site. One iMIS site usually has several. See Main website.

A group of recipes for one kind of work, such as membership or events. See Recipes.