Issue Summary

If an admin changes an external user security policy to be non-billable, so that it can't enforce SSO, there is no way of changing the policy back to being billable. This, combined with the limitation of not being able to create multiple policies (ACCESS-1952 – Allow Multiple External User Security Policies) creates a state where the admin can't enforce SSO on external users any more.

Steps to Reproduce

1. Create an external user policy.
2. Set the policy to be non-billable

Expected Results

The admin should have the ability to change the policy to be billable again so that they can enforce SSO on external users.

Actual Results

After making the policy non-billable there is no option to make the policy billable again. So, SSO can't be enforced.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available