How to manage Altassian guard with external users from company domain, but available in the IDP

[Léo Dumortier]

Hello,

We want to implement Atlassian Guard.

We wonder how to manage accounts that are not in the company domains (suppliers), but that we can manage on the ID Provider.

We'd like to know who pays guard, who manage the account, what are the good practices ?

[Janessa Drainville · Accepted solution]

Hi @Léo Dumortier! 😃 We answered these questions on a recent Guard AMA, so 'wanted to share with you here! ✨

All excellent questions! We’ll go in order of ask:

• “How should we manage accounts for external users through Atlassian Guard?” We know it’s important that external or temporary users do not need to be added as managed accounts for your organizations so Atlassian has special external user security controls. Essentially, you can require an extra step of security when external users try to access your organization’s data. When you enable single sign-on, you will have to sync external users from your identity provider so they are not blocked from accessing the help portal. That’s it!

• “Who is responsible for paying for Guard licenses for these users?” External users with full product access are generally billed at the same rate as managed users. The billable user count for Guard Standard includes both managed accounts and billable external users. 

• “Who manages their accounts?” Your Org Admins! They can view billable external users via an export in Adminhub.

• “Are there any best practices for handling this setup?” We do have some public facing documentation here - https://support.atlassian.com/security-and-access-policies/docs/who-are-external-users/

'Hope this helps! 💙