Back to product
Atlassian Marketplace readiness

External Share for Jira, built for secure stakeholder access.

This page explains setup, permissions, data handling, and support expectations for Jira admins reviewing RapidPelican from the Atlassian Marketplace.

Admin setup flow
1

Install RapidPelican in Jira Cloud.

2

Create a share link from an issue, board, filter, or JQL view.

3

Send the external portal URL to a client or vendor.

4

Track views, access denials, comments, and updates from activity logs.

Permissions and data handling

Forge calls Jira as the installed app to fetch shared issue data and write approved external comments back into Jira.

Attachments uploaded by external users are stored as native Jira attachments. RapidPelican stores link, session, rule, and activity metadata needed to operate the portal.

Public pages proxy attachment access through the share session, so raw Atlassian media URLs are not exposed in portal content.

Security controls

Password and magic links

Email, domain, and IP restrictions

Rule-aware session invalidation

Native Jira attachment storage

Support and marketplace review

Use this route for Marketplace reviewers and Jira admins who need a concise security, setup, and support summary before installing.

Jira Cloud focused