Jump to content

You can now start using single sign-on to verify the identity of your external users. You'll be able to configure all user security from one place  – your identity provider.  When you connect your identity provider and set up SAML single sign-on (SSO) , you can enforce SSO in your external user policy.

SSO counts towards Atlassian Guard Standard bill
When you enable SSO in an external policy, we bill you for the external users in the policy. When you select one-time password or none as the authorization method, we don’t bill you for the external users in the policy.

Here’s a summary of what is and what is not billable for Atlassian Guard Standard
External user counts as billable
External user is in a billable external user policy and has product access to Jira, Jira Service Management, and Confluence.

External user doesn’t count as billable
External user is in a billable external user policy and has product access to Enterprise versions of Jira, Jira Service Management, Confluence, and Trello. And also for Statuspage: Startup, Business, and Enterprise

User has no product access to Jira or Confluence
External user is in a non-billable or test policy

Understand external user security

Before you begin:
Subscribe to Atlassian Guard Standard from your organization. Understand Atlassian Guard
Make sure you're an admin for an Atlassian organization.
Add an identity provider directory to your organization. How to add an identity provider
Configure SAML single sign-on with an identity provider Configure SAML single sign-on with an identity provider

To enforce single sign-on:

  1. Log in to admin.atlassian.com > Security > External users.
  2. Select the External user policy.
  3. Select Single sign-on.
  4. Select the Identity provider you use to manage single sign-on.
  5. Select Update.

View full product update

  • Replies 0
  • Created
  • Last Reply
Expand topic overview

Featured Replies