We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

What is an external user security policy?

An external user policy allows you to apply security settings to external users. These settings apply to all external users in your organization. For example, if you need external users to verify their identity with single sign-on, you can apply require it through this policy. You can also apply session expiration and block user API tokens. Available external user security policy settings

Non-billable policy

Users in an external user policy count towards your Atlassian Guard Standard bill. A non-billable policy gives you the flexibility to choose whether or not to include external users in your Atlassian Guard Standard bill. Users in a non-billable external user policy don’t count towards your Atlassian Guard Standard bill. In a non-billable policy, you can only require one-time passcode, set session expiration, and control user API token access. You can’t require single sign-on. Make external user policy non-billable

Test policy

A test policy lets you test external user security settings with up to 5 users before you roll them out to all your external users. If you have Atlassian Guard Standard, the users in your test policy don’t count towards your Atlassian Guard Standard bill. Add a test external user policy

Atlassian Government Cloud

An external user policy lets you set SAML single sign-on for external users, which is a customer responsibility requirement for Atlassian Government Cloud organizations. A non-billable policy isn’t available in Atlassian Government Cloud environments because you don’t have an Atlassian Guard subscription.

Still need help?

The Atlassian Community is here for you.