---
title: Troubleshooting Guide: Single Sign-On with Okta
slug: portal-sub/troubleshooting-guide-single-sign-on-with-okta
docTags: 
createdAt: 2026-03-04T12:03:15.621Z
---

# Overview

This guide provides some troubleshooting tips relating to Profile's ability to use Okta for Single Sign-On (SS)). 

It is written specifically for someone in a System Administration type role, and will cover the following issue:

- What can I do if a user is locked out of Profile?

# Troubleshooting for SSO with Okta

## What can I do if a user is locked out of Profile?

::::WorkflowBlock
:::WorkflowBlockItem
### Confirm that the Profile user's Okta username is correct, and that the checkbox has been enabled.

1. Go to **Organisation** / **People & Places**
2. Find and double click on the provider needing access to SSO.

::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/Pdqrjyq4-mOdA1W-WdpIp_y5qa6rzwg2djifcazx512mczfkoj2nifa.png" size="100" isUploading="false" initialPath="assets/Y5Qa6RzWg2dJIfcaZx512mcZfKO_J2nIfA.png" githubPath="en/General Settings and Configuration/Single Sign-On/Okta SSO/assets/Y5Qa6RzWg2dJIfcaZx512mcZfKO_J2nIfA.png" position="flex-start" showCaption="false" indent="2"}

3. Go to **Special**
4. Make sure that the **Okta Username&#xA0;**&#x63;heckbox has been checked, and that the provider's **Okta Username**, found here, is the same as the provider's username found within Okta.You can make this comparison by going to Okta's Admin Console - **Application&#xA0;**/ **Application** /**&#xA0;Assignments&#xA0;**&#x74;ab / **Person**.

::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/qMp6-ZbQRxCzIIqvdu9cP_km8ayzbsfkknsc681-pyweiytrrv01d8ka.png" size="100" isUploading="false" initialPath="assets/Km8AYZbSFkKNsc681-PyWeIyTRRV01D8kA.png" githubPath="en/General Settings and Configuration/Single Sign-On/Okta SSO/assets/Km8AYZbSFkKNsc681-PyWeIyTRRV01D8kA.png" position="flex-start" showCaption="false" indent="2"}
:::

:::WorkflowBlockItem
### Check that the user has signed up with Okta.

1. Users must be signed up with Okta in order to access the Okta SSO capabilities in Profile. 
2. Go to the Okta Sign In screen and enter in the user's login details. If the user is not signed up with Okta, the user will not be given access to go past this point.

::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/mj_zC3wIfSqg9iWr599R7_cbq7h1zesk1estfyjzc0gnaku9pneaf-nw.png" size="70" isUploading="false" initialPath="assets/CBQ7H1zeSk1eSTfyjzC0GnAkU9PnEAF-Nw.png" githubPath="en/General Settings and Configuration/Single Sign-On/Okta SSO/assets/CBQ7H1zeSk1eSTfyjzC0GnAkU9PnEAF-Nw.png" position="flex-start" showCaption="false" indent="2"}
:::

:::WorkflowBlockItem
### Make sure that you have assigned the Okta username to the Profile application on the Okta admin side. 

1. Go to your Okta environment **Applications** / **Applications** / You&#x72;**&#xA0;**&#x50;rofile application / **Assignments** tab.
2. If the user's name is not found in the **Person&#xA0;**&#x63;olumn of the assignments directory, they will not be able to access Profile.

::Image[]{src="https://api.qa.archbee.co/api/optimize/zICxj0dnLereb6UUrBA3-/jei7ZkvSxSCJWnqsSkHkl_0pvqvi29gdldcf2ihamdqpz-mcjbcecr2a.png" size="89" isUploading="false" initialPath="assets/0pvqVi29gDLDCf2IhamDqpZ-mcjBCeCr2A.png" githubPath="en/General Settings and Configuration/Single Sign-On/Okta SSO/assets/0pvqVi29gDLDCf2IhamDqpZ-mcjBCeCr2A.png" position="flex-start" showCaption="false" indent="2"}
:::
::::
