0

Set Up Committees in Forumbee for iMIS Managed Access

This guide shows a simple, repeatable way to create committee spaces in Forumbee, lock them down to members, and let iMIS committee membership control access.

This article assumes you have already completed the iMIS SSO setup and IQA configuration described in the first two guides.

What you will build

For each committee, you will create:

  • A private committee category in the Committees section
  • A matching access group, for example {Committee Name} Access
  • A mapping from the iMIS committee identifier returned by IQA to the Forumbee access group

Once set up, users will be added to the right access groups when they sign in through iMIS SSO.

Prerequisites

  • The Committees section already exists in Forumbee, or you have a section where committee categories will live
  • The iMIS SSO integration is configured and working
  • Your iMIS IQA returns the committee identifier you plan to map (often a committee code, but it can be a name if that is what your IQA returns)

Step 1: Create a committee category

  1. Go to Admin > Categories.
  2. Click Add Category.
  3. Select Discussions.
  4. Set Category Name to the committee name, for example Committee for Physician Wellness and Resilience.
  5. Under Section, select Committees.
  6. Click Save.

Set the category to private

  1. In the category, expand Access.
  2. Set access to Specific Members.
  3. Click Save.

Recommended category settings

These settings work well for private committee spaces:

  • In Notifications
    • Enable category following: ON
    • Auto-notify all users: ON
  • In More Options
    • Enable events calendar: ON
    • Enable members tab: ON

Keep other settings at their defaults unless you have a specific need.

Step 2: Create the access group and grant category access

  1. Go to Admin > Users > Groups.
  2. Click Add User Group.
  3. Name the group {Committee Name} Access, for example Physician Wellness and Resilience Access.
  4. Click Save.
  5. Open the group and expand Access.
  6. Check the corresponding committee category.
  7. Click Save.

Step 3: Map the iMIS committee identifier to the Forumbee group

  1. Go to Admin > Integrations > iMIS SSO.
  2. Open Group Mapping.
  3. Click Add Mapping Row.
  4. Select the Forumbee group you created.
  5. In iMIS Committee ID, enter the exact value that your IQA returns in the column you configured as Committee ID Column.

Important:

  • The iMIS value must exactly match what your IQA returns, including spaces and capitalization.
  • Some clients map using a committee code, and others map using a committee name, depending on what the IQA returns.

Click Save.

Step 4: Choose how removals work

In Group Mapping, review the setting:

  • Remove users from mapped groups when committee membership is missing

When enabled, Forumbee removes a user from iMIS managed groups if the user no longer appears in that committee in iMIS.

Notes:

  • Forumbee only removes users from groups that are part of the mapping table.
  • This avoids removing users from groups that are managed manually.

Step 5: Validate the setup

Use this checklist:

  • The committee category is private and not visible to users who are not members
  • The access group has access to the committee category
  • The iMIS group mapping row is saved and uses the exact committee identifier returned by IQA
  • A test user who is in that committee signs in through iMIS SSO
  • After login, the test user can see the committee category and receives notifications based on your category settings

Reply

null
Login to reply

Content aside

Related Articles
Set Up iMIS SSO for Forumbee
Configure iMIS IQA for Committee Sync and Profile Field Mapping
Set Up Committees in Forumbee for iMIS Managed Access
Troubleshooting iMIS SSO and Committee Access Sync