This integration supports Khoros Communities on the Classic framework. Communities on Khoros Aurora aren’t supported yet, and Oleria tells you so when you connect one. Khoros Care and Khoros Marketing aren’t covered by this integration.
What Oleria discovers
Once connected, Oleria continuously discovers and maps the following from your Khoros community:- Accounts - community members, with their login, email address, ban status, single sign-on ID, and last visit. By default, Oleria imports only members who hold at least one role, which keeps large public communities manageable. You can choose to import every member instead, for example for a private or employee community. Members with the Administrator role are marked as administrators.
- Roles - every role in the community at every scope: community-wide roles, and roles on a category, a board, or a group hub. Each role shows the scope it applies to.
- Role membership - which members hold each role. Membership of a group hub appears as that hub’s member or owner role.
Oleria doesn’t import boards, messages, or other community content. The Khoros Community API doesn’t provide an audit log or sign-in history, so this integration has no activity data.
Prerequisites
- A dedicated local community user for Oleria with the community-level Administrator role. It must be able to sign in with a password, and it must not be banned. An account that can only sign in through single sign-on can’t be used.
- Your community’s address, for example
https://community.example.com. - If Khoros CommunityGuard blocks automated requests to your community, a CommunityGuard API access token from Khoros Support.
- Admin access to the Oleria workspace.
Create the Oleria user in Khoros
1
Create a local user
In your community, create a new local user for Oleria, for example with the login
oleria-api. Give it a strong password and make sure it can sign in with a password rather than only through single sign-on.2
Give it the Administrator role
In Community Admin, assign the user the community-level Administrator role. Oleria needs it to see members’ email addresses and ban status, and Khoros allows role and ban changes only to administrators.
3
Keep the account for Oleria only
Don’t use this account for anything else, and don’t change its roles from Oleria. Oleria refuses to remove its own Administrator role or ban itself.
Connect Khoros to Oleria
1
Open the integration
Go to your Oleria workspace, select Integrations -> select Khoros.
2
Complete the connection form
Select Continue and provide the following:
3
Confirm the connection
Select Authenticate. Oleria signs in as the user, checks that it holds the Administrator role and can see members’ email addresses and ban status, and checks that it can read the community’s roles. Find the newly connected community on the Connected tab of your Oleria Integrations page.
You can connect each Khoros community to Oleria once. If you change the login or the Community URL when you edit the integration, enter the password again. If you change the Community URL and your community needs a CommunityGuard token, enter the token again too. To keep the stored password when you edit only other fields, leave the field empty. A stored CommunityGuard token can’t be removed from the edit form yet; to remove it, delete and re-add the integration.
Verify the integration
Confirm the Khoros community appears on the Connected tab of your Oleria Integrations page with a status of Healthy. After the first sync completes, you can review the discovered accounts, roles, and role membership in your Oleria workspace.Remediation actions
Oleria can take these actions in Khoros:- Add a member to a role, at any scope. This includes adding a member to a group hub through its member role. Reverting the action removes the role again.
- Remove a member from a role. Reverting the action adds the role back.
- Ban a member. In Oleria this action is labeled Disable account. The member’s roles and content are kept, and nothing is deleted. Reverting the action lifts the ban.
- Unban a member. Reverting the action bans the member again. The original ban’s reason and expiry can’t be restored through Khoros’s API, so the new ban is permanent until lifted. Set an expiry in Mod Tools -> User Bans if the original ban was temporary.
- Oleria won’t remove the Administrator role from its own user or ban its own user.
- A revert is refused if someone changed the member in Khoros after the action, so a later change is never overwritten.
- If Khoros grants a role automatically through a rank, removing that role doesn’t stick. Change the member’s rank in Khoros instead.
- Unbanning lifts a ban set on the member. Bans by email address or IP address are managed in Mod Tools -> User Bans.
- If Oleria can’t confirm whether a change was applied, the action reports that it may have been applied and states how to undo it in Khoros. Check the member before running it again.
Known limitations
- Communities on Khoros Aurora aren’t supported yet.
- Oleria doesn’t import two-factor authentication status, API apps, or session keys.
- Khoros has no audit log or sign-in history API, so there’s no activity data for Khoros.
- With the default Members holding a role setting, members who hold no role aren’t imported. Choose All members for private or employee communities where membership itself is the access.