Restricted resource error message

1 Introduction
2 Understanding Shared Resources through External Share for Jira
3 Reasons for "Restricted Resource" Message:
4 Guidance for Internal Users on Ensuring Access to Shared Resources:
5 Conclusion

Introduction

External Share for Jira enhances Jira by making internal content—including individual issues, boards, timelines, and filters—accessible to external users via shared links.
However, there can be instances where a "Restricted Resource" message is displayed for these external users. This documentation explains the causes of this message and offers guidelines for internal users to ensure uninterrupted sharing.

Understanding Shared Resources through External Share for Jira

Jira, by default, doesn't provide a way to share its content with external users.
External Share for Jira fills this gap by offering shareable links to internal content.
But, instead of storing this data, External Share for Jira fetches it in real-time when accessed.
This is achieved through API calls, which operate as if they were made by the last internal user who modified the shared link. As a result, the accessibility of these shared links is closely tied to that particular user's status and permissions.

Reasons for "Restricted Resource" Message:

User's Access Revoked: If the internal user who last modified the share no longer has access to the shared resource (e.g., issue, board), external users trying to access this shared link will encounter the "Restricted Resource" message.
Internal User is Inactive or Removed: If the user responsible for the share becomes inactive (suspended) or is removed from the Jira instance, the shared resource is locked out.

Guidance for Internal Users on Ensuring Access to Shared Resources:

Update Access Permissions:

Confirm that the internal users associated with shares are active and possess the required permissions.
If an internal user's status changes or they're removed from Jira, make sure the related shares are updated or reassigned to another active internal user.

Conclusion

Understanding that this issue is commonly tied to the status and permissions of the last internal user who modified the shared link provides a clear pathway for internal users to manage and prevent this issue. To ensure uninterrupted sharing, internal users should diligently maintain active statuses and the necessary permissions. In cases where an internal user is either suspended or removed from Jira, timely reassignment or update of the shared resources is essential.