Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

is it ip address restriction available in premium?

We are using free accounts and are considering getting the Premium Plan specifically for restricting access by IP addresses.

Based on info I've seen so far, it's per repository, but I am not sure. Specially that there is no trial for the premium plan to check this.

Our requirement is that some users will be using a specific IP address, while others are not restricted.

My question is that is how flexible is is this IP restriction? Can it be set per user?

Is it set at the repository?

Or is it a global setting for all users in our organization? Not sure if this is possible though.

If the setting is indeed per repository, would it be a problem that some users (developers) of the repository will be restricted by IP while others (project managers) are not?

Thanks in advance!
Is IP whitelisting per user, per repository, or global (not sure if this applies) for Premium plan?

1 answer

0 votes
Syahrul Atlassian Team Jul 07, 2022

Hey @Sukhil P S 


The IP Allowlisting feature is not per repository. It's on the Workspace level. 

When enabled, this will require that users with access to private repositories or other private content are only able to see the content from specific IP addresses. If they aren't accessing from allowlisted IP addresses, users will see a message explaining why they have no access. In addition to being unable to see this content, users won't be able to clone, push, or pull a private repository either.

Currently, it's not flexible where you can have specific users bypass the feature. Since it's on the Workspace level, all users that have access to your Workspace will have to use IPs that were allowed when accessing your Workspace.

For more information on this, please check our KB at:


Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events