外部ユーザー セキュリティとは

People in your organization may collaborate with users whose Atlassian accounts you do not manage. We call these external users. To understand the difference between managed accounts and external users, see: What are managed accounts?

管理者はこうした状況において、次のような方法を実行できます。

• 外部ユーザーにアクセス権を付与して、従業員とのコラボレーションを促進する

• データへの望ましくないアクセスを防ぐ

External user security helps you protect data in your organization. You can require an extra step of security when external users try to access your organization’s data. Configure an external user security policy

Example of external user security

This is an example of how external user security works.

1. A user logs in to Atlassian to access Confluence in an organization called Bancly Inc.

2. They open a Jira work item from another organization, Acme Global. Acme Global’s external user policy requires external users to verify their identity to view content.

3. The user verifies their identity with a one-time passcode. They can now view the Jira work item in Acme Global.

External user security in apps

External user security settings apply to external users in your Atlassian organization that use these apps:

• Confluence (including Confluence guests)

• Jira

• Jira Service Management (Atlassian アカウントのみ)

• Jira Product Discovery

We also block external users from viewing your organization's app data through mobile push notifications.

外部ユーザーによる公開コンテンツへのアクセス

An organization may make content available to anyone on the internet, which becomes public content. Anyone can view public content anonymously, but external users may find they need to verify their identity to view the same content if they log in to their Atlassian account. This can happen when you apply external user security to your organization.

外部ユーザー セキュリティの制限

External user security settings don't apply in some cases. We won't verify the identity of external users when they:

• view in-app notifications

• view data through AppLinks