Manage Authentication in Bulk (BBID)

As a platform manager, from Core, select Security and then Blackbaud ID authentication. Users will appear in the list that corresponds to their authentication status for Blackbaud ID.

Registered indicates the user has a Blackbaud ID username and has signed in with it at least one time.

You can Disconnect users who should no longer log in. You can also disconnect users who need to switch to a new username (email address). When you disconnect users, they become unregistered, but you connect them with a new email address.

By default, users who have been manually disabled or disabled automatically due to inactivity are hidden from the list. To view them, clear the Hide disabled filter and then enable the Column for Disabled. Select the column header to sort the list. List managers can also view them in the Users list.

Unregistered indicates the user does not log in at all.

When you choose users from this list and then select Connect, each users' contact email address becomes their Blackbaud ID username, which they'll use to login. They'll setup passwords during their login experience.

Consider selecting to also send email "invitations" with instructions for users to follow as they connect with Blackbaud ID. The email invitations include automatically generated content. The email addresses used as recipients are the same contact email addresses used as the Blackbaud ID usernames. Each invitation is valid for 30 days. If a user's invitation expires, consider reinviting them.

Awaiting response indicates the user has a Blackbaud ID username, but has not signed in with it yet. The user will be required to sign in with Blackbaud ID the next time they log in.

You may want to remind these users to log in soon; consider sending an other email with instructions for users to connect with Blackbaud ID. Do this, select to "reinvite" the users. Each invitation is valid for 30 days. If a user's invitation expires, consider reinviting them.

If you reinvite a user whose contact email address has recently changed, the email address initially invited to connect to Blackbaud ID is used for the username and as the email recipient.

To change the email address used for Blackbaud ID, Disconnect the user first (which makes the user "unregistered"), and then Connect the user with a new email address.

By default, users who have been manually disabled or disabled automatically due to inactivity are hidden from the list. To view them, clear the Hide disabled filter and then enable the Column for Disabled. Select the column header to sort the list. List managers can also view them in the Users list.

Consider disabling the accounts of users who withdrew as students or who are no longer employed as faculty, to prevent them from logging in.

  1. From the list ofUnregistered users, use Search and the Filters to locate users.

  2. Select one or more users.

  3. Select Disable and confirm you no longer want them to login.

Accounts may be disabled because they are

  • an admin disabled them,

  • locked (such as due to too many failed login attempts),

  • or inactive (due to no activity for 395+ days) and thus disabled for security reasons. These users continue to receive PushPages (Newsletters), emails, and notifications that they’ve opted into.

The reason appears in the Warning column for Unregistered users. Alternatively, list managers can use the Disabled column filter on the User list to review which accounts have been disabled, locked, or inactivated.

To enable a single account, a user contacts the school. Then a platform manager goes to the user’s profile in Core, selects Access, and changes Disabled account to No. The status changes appear in the user’s Login history.

To enable accounts in bulk, select them from the list of Unregistered users. A message appears to summarize the accounts included in the bulk action. Confirm the change. If an account can't be enabled in bulk, the reason appears in the Warning column.

After accounts are enabled, you can invite them to login with Blackbaud ID,

When handling users in the Registered, Awaiting response, and Unregistered lists, platform managers can determine how many items to show per page. To quickly Enable, Connect, Re-invite, or Disconnect users in bulk, select to show a large number (such as 500). Platform managers can invite up to 2,500 users at one time. To invite more, send invites in batches of 2,500 or fewer.

Use the lists to select a subset of users to manage in bulk. From each list, use the Search, sort options, and Filters to limit the results to the users you want to update. For example, you can filter to show registered users with student role, search for specific grad year, and sort by SSO email address.

Some authentication settings are not accessible while impersonating. To set up authentication for your school, log in as the platform manager who has organization admin rights instead of impersonating one.

If you run a User management type of Data import job to assign Blackbaud ID usernames, the next login experience for those users will be affected.

As a platform manager, filter the list of Unregistered users and select which users to Connect.

The SSO column shows the email domain for any users that have a contact email that is on an email domain configured for SSO. Select these users and then select Connect.

This sets their Blackbaud ID username to their contact email . The next time the user logs in, they’ll use the email address on the login page for their new login experience.

parents or alums)

As a platform manager, filter the list of Unregistered users and select which users to Connect. This sets their Blackbaud ID username to their contact email.

To login, they’ll use their email address as their username on your school’s login page and enter their password on the Blackbaud ID sign in page.

Alternatively, select a single user's name to go to the Access tab of the user's profile to manage the individual's authentication settings. You can also use the People finder in Core to go to the Access tab of the user's profile to manage the individual's authentication settings. From the individual’s Access options, you can send the user an email with an invitation to create their Blackbaud ID account using their email address as the username.

Platform managers can update authentication for students who graduate and become alums.

Ensure your school has correct and current email addresses to contact students after they graduate. These email addresses will be used to login as alums.

To handle graduating seniors who previously used single sign ons (SSO), you’ll first disconnect the existing Blackbaud ID usernames (the ones used for SSO as students).

  1. To do this in bulk from Core, select Security, and then Blackbaud ID authentication.

  2. Filter the list of Registered users so that it shows the current grad year, roles of alum or student, and individuals whose contact email address matches your school domain for SSO.

  3. Select the individuals who need to use a new email address for their login and then select Disconnect.

Review the contact email addresses of the disconnected grads to ensure that they use personal email addresses instead of school email address. You may need to update the contact email addresses for the grads that you disconnected to use personal email addresses.

Next, you’ll connect the same graduate users to create a Blackbaud ID link with their personal email address.

  1. To do this in bulk from Core, select Security, and then Blackbaud ID authentication.

  2. Filter the list of Unregistered users so it shows the recent graduates.

  3. Select the individuals who need to use a new email address for their login and then select Connect.

The next time a graduate attempts to login using their old username, the user is prompted to create a new Blackbaud ID with their new email address. The user authenticates and links it to their school account for ongoing access as an graduate or alum.

To interact with your peers at other schools and follow blog posts aboutBlackbaud ID, visit the Blackbaud User Community online.

Remember that the email address used forBlackbaud ID must be unique. It can’t be used by other users. Typically, the primary email address from a user's contact card will become the user's Blackbaud ID username. However, you can use a different email address for authentication when desired.