Specify IP addresses for app access

Use an IP allowlist to specify which IP addresses users must use to access content in Jira, Jira Service Management, Confluence, Compass and Atlassian Analytics.

If your organization uses restrictive firewall or proxy server settings, you or your network administrator may need to allowlist certain domains and IP address ranges.

IP 許可リストの制御は次に適用されます。

• Compass

• Confluence のスペースとページ (公開リンクを含む)

• Confluence 管理

• Jira tasks, issues, projects and forms (including public forms)

• Jira Service Management customer and agent-facing portals within the same site URL

• Jira 管理

• Atlassian Analytics

• Rovo*

If users attempt to access these pages from an IP addresses that is not in the allowlist, they’ll see a message explaining why they don’t have access. Users also won't be able to access that app programmatically via the APIs.

If users access your apps from a Chrome browser, it's possible that their IP address doesn't update when they connect to a different network. This is an issue if their new address is in an allowlist. If this happens, tell your users to clear their browser's cache by entering these keys: Ctrl/Cmd + Shift + R.

Rovo*

Rovo is designed to serve you information across apps. However, IP allowlist controls for individual apps, such as Jira and Confluence, don’t apply to all Rovo features.

Admins can apply IP allowlisting controls to Rovo experiences at the organization level. These controls apply to specific Rovo experiences such as:

• Rovo Chat and Search accessed via Projects, Goals, Teams, Home, and Studio apps

• Rovo ブラウザ拡張機能

• Rovo ブックマーク

The IP allowlisting controls are designed so that only users from approved IP addresses can interact with these Rovo experiences.

IP allowlists for Rovo apply to these experiences at the organization level. i.e. if you have multiple sites in your organization, the same IP conditions will apply to the above Rovo experiences regardless of the site.

Once configured, if a user interacts with Rovo from an IP address that is not in the allowlist for Rovo experiences, the user will see an error message.

IP 許可リストを表示する

IP 許可リストを表示するには、次の手順に従います。

1. 移動 Atlassian Administration. Select your organization if you have more than one.

2. Select Security > Device security > IP allowlists.

You will be able to access admin.atlassian.com even if the IP is outside the range of the allowlist.

許可リストを追加する

許可リストを追加するには、次の手順に従います。

1. 移動 Atlassian Administration. Select your organization if you have more than one.

2. Select Security > Device security > IP allowlists.

3. [許可リストを作成] を選択します。

4. 許可リストの名前を入力します。

5. Select the names of the apps you’d like to add to the allowlist.

6. 許可する IP アドレスを入力します。最大 500 個の IP アドレスをコンマ区切りで入力できます。

7. 許可リストをすぐに有効にするか、後で有効にするかを選択します。

8. Select Create to save the details.

どのような値を追加できますか?

You can set up 500 IP addresses or network blocks per app. We support IPv4 for individual IP address. If you're entering a network block, we support the CIDR notation standard for specifying a block of IP addresses. Refer to CIDR notation more details about how to use CIDR notation.

追加できる値の例をいくつか挙げます。

IP 許可リストの例外

場合によっては、IP 許可リスト内のユーザーに対して Jira、Jira Service Management、Confluence の特定の情報に対するアクセスを制限できないこともあります。

IP 許可リストに関係なく、ユーザーは次の情報タイプを常に閲覧できます。

また、次のものには IP 許可リストの制限が適用されません。

• Application links that use 2LO

• アプリの接続

• Forge apps with 2LO and 3LO

• OAuth 2.0 (3LO) apps

Third-party security tools

If your organization uses security platforms like Zscaler [Source IP Anchoring] that proxy internet traffic, you may need to exclude Atlassian domains (*.atlassian.com, *.atlassian.net, *.atl-paas.net) from proxying in your platform's configuration or add your security platform's IP ranges to your allowlists. These platforms may use different IP addresses for application access and other content, such as media, which can block some content even if users can access the main application. Contact your security platform provider for specific IP ranges and configuration guidance.

Performance tip: For optimal performance, configure your security platform to skip TLS/HTTPS inspection on *.atl-paas.net domains.