Is it possible to grant access to an external organization (with or without atlassian account)

[Fred Cassado]

Is it possible to grant access to my Jira "project new generation" to external organization ?

I don't want to pay new licence, but my customer could open account (or may be not if possible) and then get connected to their "project new generation" (like I give them access into project parameters).

I don't want them to see "all my project" but only the project I gave them access.

How can I manage it ?

Do they have just to get an atlassian account for jira ?

Then how do they request access ? Or can I give them access without getting a licence on my side ?

Please could you guide me ?

Thanks by advance

Best regards

[Jack Brickey]

Anyone that needs access to Jira must be licensed. You can control what projects they have access to via the project settings of the project.

[Harry Rombach]

understood. In case of our consultants they are double licensed. They have already a licence and we need to buy another one for them to let them collaborate with us. Is this the game? I would appreciate a federation where people only need one licens from you and can work in the diverse accounts. What are your thoughts on that?

[Markus Wages]

I guess this answer doesn't really fit to the question. Imagine Tom is a consultant with an enterprise having e.g.  Jira use rights. Tom has a customer A also using Jira A gives Tom a license. Tom works also for customer B and C all using Jira. At of the story Tom has 4 use rights allocated. You sell a named user license. From my perspective 1 use right for Tom should be sufficient. It is a named user license.

[Jack Brickey]

@Harry Rombach each instance requires a separate user license. Licenses aren't per user globally where they can log into any instance. One thing I did want to make clear here is that I do not work for Atlassian. I am a user like yourself.

[Harry Rombach]

got your point. Can you give me a hint how to bring this topic to the attention of Atlassian?

[Fred Cassado]

@Jack Brickey OK, understood. That means that in Jira you can't be an external consultant (on Jira integration by the way) or any consultant in website development like ourselves. If we need to get involved into Customer A projects/Jira instance and get involved in Customer B projects/license, this means that I need to get a licence for A & for B. 2 licences ? 

(and I don't talk of the idea to get issue from one instance A, to copy in instance B or in my company instance C to share the job in my teams in between A & B project)... it starts to be expensive and not really efficient, I think.

Many thanks for your answer.

BR,