Can an external JPD contributor + JSM portal-only customer remain non-billable under Guard

[Yousif Hassan]

Hi everyone,

I’m trying to confirm whether this setup can remain non-billable under Atlassian Guard.

We have an external user who is not part of a managed domain, and we want that same person to have both:
- Jira Service Management portal-only customer access
- Jira Product Discovery contributor access

We already understand that JSM portal-only customers can be handled through an external user policy, and that JPD contributors are generally described as non-billable on their own. What I’m trying to confirm is the combination of the two, especially where we want to use SAML 2.0 / SSO through Atlassian Guard.

So the question is:

If the same external user has both JSM portal-only access and JPD contributor access, can they still remain non-billable under Atlassian Guard when SSO is enforced, or does enabling SSO make that user Guard-billable?

Thank you appreciate the support :) 

[Olga Springer · Accepted solution]

Hey

This is how it works as of today:

If the same external user has both JSM portal-only access and JPD contributor access, they remain non-billable under Atlassian Guard when SSO is enforced.

Best,

Olga Springer
Senior Product Manager, Jira Product Discovery

[Yousif Hassan]

Oh Olga that is amazing news. Thank you so much :) 

[Kunal Tambi]

Hi,

This setup will not remain non-billable once SSO is enforced via Atlassian Guard.

While Jira Service Management portal-only customers are non-billable, and Jira Product Discovery contributors are also typically non-billable from a product licensing perspective, Atlassian Guard billing works differently. Guard billing is based on whether a user is subject to authentication policies like SSO and whether they have any application-level access.

In this case, since the same external user has Jira Product Discovery contributor access, they are no longer considered a portal-only user. If SSO is enforced on them through Atlassian Guard, they will be treated as a managed user under an authentication policy, which makes them billable under Guard.