External (Atlassian Access) domain user access to specific projects in our site

[Benjamin Barniskis]

We use Okta and Atlassian Access for all internal Jira users.

We have a vendor that we are collaborating with that also has Jira (and Atlassian Access).

I am trying to figure out the best way to invite them to a specific project. I understand the permission schemes (browse all projects and what not) so I can limit their project access.

I am trying to figure out the best way to leverage their existing (external) Atlassian Access, so we don't need to create an external user in our Okta just so they can access our project.

1. How do invite their existing external Atlassian Access user account to our site?
2. Can I do this without granting them Product access?
   1. They already have Jira Software Product in their site
3. Can all this be done without having them as a billable user to our site?

[Walter Buggenhout · Accepted solution]

Hi @Benjamin Barniskis,

The external Atlassian Access is not relevant for your use case. The good thing is that your external user already has an Atlassian account, identified by his/her email address.

If you want to add that user to your site, you can invite him/her with that email address. If you want to provide that user access in Jira software on your site, you do need to grant product access to JSW on your site to that user. He will take up a license seed on your instance, as a license is linked to an Atlassian product in a site - it is not linked to a user.

Hope this helps! 

[Benjamin Barniskis]

Thank you Walter.

Do any of the Access policy configurations apply to those external users?

I get that I would need to add a product license for the external users to update our Jira items, but can I add an access policy to their accounts even though they are external?

I am looking for some control/identification of the external users in our site, but also to limit our costs by eliminating the Okta user we current set them up with.

[Walter Buggenhout]

You could just create a group in your Atlassian Admin / Groups for external users and then add that group to product access, alongside the default access group you would normally use for your internal users.

Adding external users to that group has several benefits:

• looking at the members of that group should give you an immediate view of the total number of external users with access to your environment;
• when a new external needs to join, all you need to do to grant a license is add the user to that group.
• revoking an external user's license is just as simple 

[Ampule Inc_]

And, how might Ben restrict external access to specific project(s), since he does not want to give the external user access to his entire internal site?

[Trudy Claspill]

@Ampule Inc_ 

Welcome to the Atlassian community.

Ben already knows how to do that through modification of Permission schemes as evidenced by his statement:

I understand the permission schemes (browse all projects and what not) so I can limit their project access.

If you need that information for yourself, please start a new Question for yourself in this forum.

https://community.atlassian.com/t5/forums/postpage/board-id/jira-questions

[Ampule Inc_]

Thanks for moderating. New question posed here.