Configure iMIS IQA for Committee Sync and Profile Field Mapping

This guide explains how Forumbee uses an iMIS IQA query to:

Identify the user with an immutable iMIS ID
Read the user name and optional email
Find committee memberships
Optionally map other IQA columns into Forumbee profile fields

This article follows the setup steps in the iMIS SSO setup guide. If you have not created and published the required IQA query in iMIS yet, start there first.

Note: IQA stands for Intelligent Query Architect and is iMIS’s query tool that can be published for API access.

How it works in plain language

During SSO login, iMIS returns a token that includes a username value.

Forumbee then calls the iMIS IQA API using that exact username value as the parameter:

GET {IQA_BASE_URL}?queryname={QUERY_NAME}&Parameter={username}

Note that the query string uses Parameter with a capital P.

The IQA response returns one row per committee membership. If a user belongs to multiple committees, multiple rows are returned.

Step 1: Create the IQA query in iMIS

Your iMIS admin or consultant will publish an IQA query that:

Accepts a single parameter, which is the literal username string from the token
Returns at least the required columns listed below
Returns one row per committee membership

Required columns in the query results

Forumbee expects these values, using the column names you configure in Forumbee:

Unique user ID (immutable iMIS identifier, often Party ID)
Full name
Committee identifier (often a committee code)

Common examples of column names:

Id, Full Name, Committee Code
ID, FullName, Committee Code

Your query can use different column names as long as you configure the matching names in Forumbee.

Optional columns

You may also return additional columns you want to map to Forumbee profile fields, for example county, specialty, location, or member type.

If iMIS usernames are not valid emails, you should also return an email column and configure it in Forumbee.

Step 2: Enter IQA settings in Forumbee

In Forumbee, go to Admin > Integrations > iMIS SSO and open IQA Configuration.

Fill in:

IQA Base URL
Example: https://{org}.imiscloud.com/api/IQA
Query Name
Unique User ID Column (required)
Full Name Column (required)
Committee ID Column (required for group sync and access)
Email Column (optional)

Click Save.

Step 3: Set up profile field mapping (optional)

If you want to populate Forumbee profile fields from iMIS:

Open Profile Field Mapping.
Add a row for each field you want to populate.
Choose a Forumbee Profile Field.
Enter the iMIS IQA Column Name exactly as returned by the IQA.

Behavior notes:

This mapping is best effort.
If a mapped column is missing for a user, login still succeeds.
If a value appears in multiple rows, Forumbee uses the first non-empty value it finds.

Verify IQA is working (using the Log tab)

Trigger a fresh SSO login (use an incognito window, or log out and log back in).
In Forumbee, open Admin > Integrations > iMIS SSO > Log.
Confirm you see an IQA request and a successful response.

If it fails, the Log tab can provide useful clues to help you or your iMIS consultant diagnose the issue.

Email sourcing rules

Forumbee must have a valid email address for the user to log in.

Forumbee chooses email in this order:

If an IQA email column name is configured and a value is returned, Forumbee uses that value.
Otherwise, Forumbee uses the token username as the email if it passes email validation.

If neither produces a valid email, login fails.

Troubleshooting tips

If IQA calls are failing, check these common issues:

The IQA base URL is incorrect, or missing /api/IQA
The query name is not published or not accessible to the API user
The query does not accept the literal username string passed as Parameter=<username>
The request uses parameter instead of Parameter
The OAuth app or service account does not have permission to execute IQA

If committees are not syncing, verify that the committee identifier returned by IQA matches the values you will map in Forumbee.