Disabling External User Access

[Alex Billings]

We are preparing to implement user provisioning via Okta, and as a result, we want to completely disable any way for users to log in with any email other than the one tied to our Okta SSO. 

 For example, users can log in with username@mycompany.com with Okta SSO, but any other email will be rejected out of hand.

 Right now there seems to be an out-of-box access policy that pretty much lets people sign up with any email address they want.  This access policy is marked as a “Default” right next to our Okta policy which confusingly is also labeled “Default”

[Belto · Accepted solution]

Users who do not have product access won't be counted towards the licensed users.

As agents, without having product access they won't have access to the knowledge base.

As customers (portal user), they do not require product access and are able to access the knowledge base if configured that way in the Project settings.

[James Thompson]

Thanks for the quick reply Belto.

So essentially there is no cost for provisioning, only for product access?

Here's the relevant ticket related to the Provisioning feature.

https://jira.atlassian.com/browse/ID-6305

[Belto]

That is correct James ;). Only licensed users (users with product access) are counted and billed.