How PortalPilot works

Where PortalPilot runs, how it reads requests, where it keeps settings and saved filters, and what it checks.

Where it runs

  • PortalPilot is an Atlassian Forge app. Its code runs on Atlassian’s Forge platform for your Jira site.
  • There is no Limbus Lab server. The app declares no outside address, so it cannot send data anywhere outside Atlassian.

The two parts

  • The portal part: the banner on the portal’s Requests page, and the full-screen PortalPilot window it opens. Jira’s own Requests page stays as it is underneath.
  • The admin part: the PortalPilot pages in Jira settings, under Apps.

How a list is read

  1. A customer opens a view or changes a filter.
  2. PortalPilot asks Jira for the matching requests as that customer, never as the app. It uses Jira Service Management’s customer request search.
  3. Jira returns only the requests that customer may see. Portal permissions and work item security levels are applied by Jira.
  4. PortalPilot combines the results, applies custom-field filters and the sort, and shows one page.

Lists, counts and exports work on up to 1,000 matching requests. Request content is read from Jira each time. It is not copied into PortalPilot’s storage.

What is checked on the server

  • The site’s PortalPilot subscription is checked first, on every call from the portal. Without an active trial or subscription, the call is refused and no data is returned.
  • Visibility is checked on every call from the portal, not only when the banner loads.
  • Admin pages check with Jira, on every call, that the person is a Jira admin.
  • The Save and share rules, and each field’s visibility, are applied on the server. Hiding a menu item is only a convenience on top.
  • If Jira cannot confirm an organisation or group membership, the check fails closed: the person is refused access, the permission or the field.

Where settings and saved filters live

In the app’s own Forge storage for your site:

  • General settings, user scopes, the fields configuration and the Save and share rules.
  • Saved filters, favourites and each person’s default view.

Settings are one set for the whole site. A change made by one admin applies to everyone.

What stays in the browser

  • Export files are built in the customer’s browser from the rows Jira returned.
  • The last screen a customer had open is remembered in that browser tab for up to 12 hours, so a reload continues where they were. Search text and custom-field filter values are not kept.

More detail

The Trust Center covers the same ground for security reviews:


Need help with PortalPilot? Contact us