Below, you find information to setup GSuite/ Google Apps and our SAML SSO apps for Atlassian Data Center & Server products. If you need our help or have questions, you can contact us via our helpdesk or book a free screen share session at

Step-by-Step Guides

Based on your user provisioning model, pick one of the following step-by-step guides.

In most cases we recommend to use GSuite with User Sync.

  • GSuite with User Sync
    Setting up User synchronisation with GSuite, as well as authentication via SAML

  • GSuite with Just-In-Time Provisioning
    Setting up authentication via SAML with GSuite and using Just-in-Time Provisioning to create/update User Accounts during login. GSuite does not support to transmit groups via SAML attributes. Hence, groups must be managed locally in your Atlassian Data Center or Server product.

  • Step-By-Step Guide for GSuite with Manual Provisioning
    Setting up authentication via SAML with GSuite for Users that already exist in the Atlassian Data Center or Server product.

Some important notes:

  • User Sync functionality is currently only available for Jira Data Center, Jira Server, Confluence Data Center, Confluence Server, & Bitbucket Data Center and Server.
  • Fisheye only supports Manual User Management.

Which Step-by-Step Guide you should pick?

Depending on your Atlassian product, you can choose from different user provisioning models. We recommend using User Sync, since it is easy to setup and maintain

In general, with GSuite we support the following ways for user provisioning:

  1. User Sync allows to sync users periodically from GSuite, but also when they log in for the first time into your Atlassian Data Center or Server product. See our detailed article for User Sync.
  2. Just in Time Provisioning allows to create and update users on-the-fly when they log in. It is not possible to send groups via SAML for GSuite. Thus, groups must be managed locally. See our detailed article for JIT.
  3. LDAP synchronisation from Active Directory. Is you instance still synchronised to your Active Directory via LDAP, you can continue to do so. Please follow the "Manual User Management" Guide in this scenario.
  4. For Manual User Management, the administrator has to has to create and update users on GSuite and your Atlassian product by hand.
    We do not recommend it. See our article for Manual User Management.

Model/FunctionAdmin EffortPro's and Con's

User Sync

  • Uses GSuite API to perform regular sync
  • Users and Groups created & updated shortly after done in GSuite
  • Users can be disabled
  • Additional attributes can be written to Jira User Properties
Just in Time Provisioning


need to manage groups locally on your product instance

  • Creates & Updates users based on information in the SAML Response during Login
  • GSuite does NOT support transmitting groups.
  • Users are only created on their first Login.
  • Users & Groups are updated only during SAML authentication.
  • Users cannot be marked disabled (as GSuite will not complete the Authentication for a deleted/disabled User)

Manual User ManagementHigh

  • Here no sync happens
  • Needs manual maintenance of 2 User bases (or is done via custom developments).

You might also find following documentation helpful: