Can multiple users use one login simultaneously?

[Falk Pietsch]

Hello,

we are going to switch from our JIRA Software Server to JIRA Cloud. Currently we have set our JIRA-instance (projects) to be "browsable" by anyone. This is very convenient for us because we dont need more rights for some people.

Since JIRA Cloud will be openly accessable we cant do that anymore and we are looking for a solution.

For JIRA Cloud we are thinking about creating one licensed account with set permissions. This account should then be used by "anyone" who just wants to browse issues. This seems possible and its also possible that multiple users can be active/logged in at the same time.

Is that a valid solution? Or do we have to fear that this implementation is not "intended" and might get restricted in future?

Are there other solutions for this case besides:
https://community.atlassian.com/t5/Jira-questions/create-user-directly-in-jira-cloud-version-without-invite/qaq-p/694917 

[Jack Brickey · Accepted solution]

You can be logged in on multiple browsers. Of course if there are edit permissions set there would be no way to know who made the change. I cannot speak to whether Atlassian might change this capability in the future.

[Bill Sheboy]

Hi @Falk Pietsch 

Yes, and...to what Jack notes:

One named user (individual person) can apparently use multiple browsers at this time, and different people doing this seems not supported by the Jira Cloud license agreement (please see the credentials section): https://www.atlassian.com/legal/cloud-terms-of-service

I respectfully suggest you discuss this with your org admin for Jira.

Kind regards,
Bill

[Falk Pietsch]

Hi,

while looking for alternatives to cover our case we discovered the ip-whitelisting-feature (https://community.atlassian.com/t5/Jira-articles/Keep-your-team-and-content-safe-with-IP-allowlisting-for/ba-p/1438293 ). 

For our company only people within our vpn need to access JIRA Cloud. Are we able to lock access to our vpn network with this feature?

With this we "open" our JIRA Cloud to "accessable by anyone" (set public) again and create the same behaviour we used to have in our JIRA Server instance:

- Anyone within vpn is able to "browse" issues.
- Only logged in users within vpn are able to edit/comment/... issues.
- no "outsider" (no vpn user) is able to access anything (no browse/..)

Kind regards,
Falk