Troubleshoot Okta SCIM User Provisioning

Article author
Updated

Overview

SCIM user provisioning automatically creates new Apollo users when you assign them in Okta, so you can manage access in one place.

If an assigned user isn't created in Apollo, your team may have reached its seat limit or the user may already belong to another Apollo team. A few troubleshooting steps can help get you back on track.

Check out the following sections to troubleshoot Okta SCIM user provisioning.

Back to Top

Manage Available Seats

 
Permission Required

You need to be an Apollo admin to manage your team's plan.

SCIM user provisioning follows your team's Apollo seat limit. If no seats are available, Apollo can't create the assigned user.

When your team reaches its seat limit, increase the number of seats to continue provisioning users from Okta.

To increase your seat limit:

  1. Launch Apollo, then go to Settings > Plan & billing > Plan overview.
  2. Click Manage Subscription.
  3. Increase the number of seats to accommodate your team's growth, then review and confirm the change.

You have now increased your team's available seats.

Back to Top

Handle Multiple Apollo Workspaces

If you add a user who already belongs to another Apollo team, Apollo sends them an invitation to join the new team instead of automatically creating a new user. They must accept the invitation before Apollo can add them to your team.

If the workspaces meet the requirements for consolidation, the user can access their old workspace for 30 days after accepting the invitation and move eligible data. Learn more about consolidation requirements and eligible data.

To add a user from another workspace:

  1. Provision them normally with SCIM.
  2. Ask the user to open the invitation email from Apollo.
  3. Click Accept Invitation.

You have now added a user from another workspace.

Back to Top

Reactivate a Previously Deactivated User

If a user was previously deactivated in Apollo and you provision them in Okta, SCIM starts the reactivation process instead of creating a duplicate user. Your team must have an available seat to reactivate the user.

If Okta displays a "delay in reactivating remote User" error, reach out to Apollo Support and include the user's email address and the full error message.

Learn more about reactivating users in Apollo.

Back to Top

Next Steps

Keep your team's access organized as you provision users and manage change in Apollo.

Configure SCIM User Provisioning for SSO Configure SCIM user provisioning in Okta and review supported provisioning behavior.
Use Single Sign-On (SSO) on Apollo Set up single sign-on for Apollo to centralize how your team signs in through Okta before you provision users.
Customize and Manage Your Apollo Plan Customize your Apollo plan and seat count to make room for newly provisioned users as your team grows.
Add, Manage, and Deactivate Users Manage Apollo users and reactivations to keep access, seats, and account status aligned as teammates join or leave.
Consolidate Multiple Apollo Workspaces into One Consolidate multiple Apollo workspaces to move eligible data safely when someone joins your team from another workspace.
Create and Assign Permission Profiles Assign permission profiles to provisioned users to give each teammate the right level of Apollo access after SCIM adds them.

Back to Top