Skip to main content

Roles & Permissions

Paraportal uses a role-based permission system to control what each person at the dropzone can do. Every action — from viewing the loading board to finalizing loads — is gated by a permission, and permissions are bundled into roles.

How It Works​

  1. An administrator creates roles (e.g. "Manifest", "Instructor", "Fun Jumper").
  2. Each role is given a set of permissions that define what holders of that role can do.
  3. Roles are assigned to customers, optionally with an expiration date.
  4. When a customer tries to perform an action, the system checks whether any of their active roles include the required permission.

A customer can hold multiple roles simultaneously, and their effective permissions are the union of all their roles' permissions.

Creating Roles​

When creating a role, you configure:

  • Title — A descriptive name (e.g. "Manifest Staff", "Tandem Instructor", "Club Member").
  • Permissions — The specific actions this role allows (see permission groups below).
  • Validity rule — How long the role lasts when assigned:
    • Indefinite — No expiration.
    • Fixed number of days — Expires N days after assignment.
    • End of year — Expires on December 31st of the current year.
  • Assignable by — Which other roles are allowed to assign or revoke this role. If left empty, only superadmins can manage it. This lets you delegate role management — for example, a "Chief Instructor" role could be allowed to assign the "Instructor" role.
  • Debt limits (optional) — The maximum amount of debt and the maximum number of days in debt that holders of this role may have. Leave a field empty for no limit. If a customer holds several active roles, the highest limit of each kind applies. A customer whose debt exceeds a limit (debt above the maximum amount, or in debt for longer than the maximum days) cannot be added directly to a load, added to the jump queue, or added to a queue entry. Moving customers between loads, and from the queue to a load, is not restricted. Debt is the negative total of the customer's balances, the same figure shown in receivables.

Permission Groups​

Permissions are organized into groups by feature area:

Loads​

  • Create, edit, and delete loads
  • Mark loads as ready (locks the roster) or move them back to building
  • Mark loads as departed, landed
  • Finalize loads

Passengers​

Every passenger action comes in two flavours: one that applies to anyone (what manifest staff need) and one that only applies to yourself. The self permissions are also limited to loads that are still in draft, so a jumper can organise their own manifesting early but cannot touch a load once it has been marked ready.

  • Add anyone to a load, or add only yourself
  • Edit anyone's passenger details (including line items, prices and payers), or edit only your own exit weight, exit altitude and jump product
  • Remove anyone from a load, or remove only yourself
  • Move anyone between loads and back to the queue, or move only yourself
  • Waive cancellation fees (manifest only) Holding an "anyone" permission also covers acting on yourself, so staff roles only need the "anyone" variants. Self permissions never trigger a cancellation fee, since fees only apply once a load has left draft.

Customers​

  • Create, edit, and delete customer profiles
  • View other customers' profiles
  • List and search all customers
  • View customer analytics

Balance & Funds​

  • Add funds to accounts
  • Edit balance entries
  • View all customer balances or only your own
  • Transfer funds (anyone's or only your own)

Credits​

  • Create, edit, and delete credit types
  • Issue credits to customers

Products & Shop​

  • View, create, and edit products
  • View, create, and edit line items
  • Purchase products for yourself or for others

Passenger Tags​

Jumps​

  • View your own jump log
  • Review and sign off on AFF student jumps
  • Review and sign off on Static Line student jumps

Reservations​

  • Manage the reservation calendar
  • View reservations
  • Cancel reservations
  • Manage reservation types

Experiences​

  • View experiences
  • Create, edit, and delete experiences

Vouchers​

  • Create and view vouchers

Jump Queue​

  • View, add to, edit, and remove from the jump queue

Receipts​

  • Look up receipts by number

Waivers​

  • Manage waiver templates
  • Review and approve/reject waiver submissions

Aircraft​

  • Create and edit aircraft configurations

Ledger & Finances​

  • View ledger accounts and transactions
  • Create new ledger accounts

Other​

  • Manage loyalty programs
  • Create and manage roles
  • Manage payment methods and VAT rates
  • Manage licenses (assign/revoke)
  • Manage digital signage devices
  • Manage jump groups
  • Manage external calendar sources
  • Configure payment integrations (Paytrail)

Assigning Roles to Customers​

Roles are assigned through a customer's profile (Roles tab). When assigning a role, the validity period is computed automatically based on the role's validity rule. For example, if a role is set to "valid for 365 days", assigning it today will set the expiration to one year from now.

Roles can also be assigned automatically through the waiver approval process — when a waiver template is configured with role assignments, approving that waiver grants the specified roles to the customer.

Tips​

  • Start with a few broad roles (e.g. "Admin", "Manifest", "Jumper") and add more specific ones as needed.
  • Use the "Assignable by" feature to let senior staff manage role assignments without giving them full admin access.
  • Roles with an end-of-year validity are useful for annual memberships — assign once, and they automatically expire at the end of the season.