Delegation

Overview

Delegation allows site administrators to grant project administrators the ability to manage Customer Portal Fields Panel configurations for their projects.

Administrator Roles

Site Administrators:

  • Full access to all configurations
  • Configure delegation policies
  • Manage global module settings
  • View and edit all project configurations
  • Set actor (impersonation) for configurations

Project Administrators (when delegation enabled):

  • Access project-specific configuration page
  • Create/edit/delete configurations for their projects
  • Limited by delegation policy

Delegation Policies

Enable for All Projects

Delegation enabled for all projects. All project administrators can manage panels for their projects.

Use when: You trust all project admins and want self-service configuration.

Disable for All Projects

Delegation disabled for all projects. Only site admins can manage panels.

Use when: Strict governance required and centralized control needed.

Enable with Exceptions

Enabled by default, with ability to disable for specific projects.

Use when: Most projects should have access, few projects need restriction.

Disable with Exceptions

Disabled by default, with ability to enable for specific projects.

Use when: You want a controlled rollout or to test the delegation feature.

Setting Up Delegation

For Site Administrators

  1. Go to Apps → Customer Portal Fields Panel settings
  2. Click Configuration Delegation tab
  3. Select Global Delegation Policy from dropdown:
    • Enable for all projects, unless specified otherwise
    • Disable for all projects
    • (Other policy options)
  4. Configure Project-specific Settings to override the global policy for individual projects
  5. Click Save Settings

The delegation settings allow you to control which projects can access and configure portal panels. You can:

  • Set a global policy for all projects
  • Optionally configure specific overrides for individual projects
  • Choose between “Use global setting”, “Enable”, or “Disable” for each project

For override policies: Add projects to enable/disable list in the Project-specific Settings table.

For Project Administrators

  1. Go to Project Settings for your project
  2. Look for Apps section in sidebar
  3. Click Customer Portal Fields Panel settings

Note: This option only appears if delegation is enabled for your project.


Project Admin UI

When delegation is enabled, project admins see a dedicated settings page within their project settings. This page provides a simplified interface focused on their project’s configurations.

What the Project Settings Page Shows

The project-specific settings page includes:

  • Configuration list - all panel configurations targeting the current project
  • Create panel button - create new configurations scoped to this project
  • Edit/Delete/Duplicate - full management of project configurations
  • Preview - test panels with real issue data
  • Export/Import - bulk operations scoped to the project

Walkthrough: Creating a First Panel as Project Admin

  1. Navigate to your Project Settings → Apps → Customer Portal Fields Panel settings
  2. Click Create panel
  3. Enter a Name (e.g., “Request details”)
  4. Select a Display Module (e.g., JSM Portal Panel)
  5. The panel is scoped to your project
  6. Optionally filter by Request Type
  7. Choose the Display Fields to show
  8. Click Save
  9. Open a request of your project on the customer portal to verify the panel appears

The actor of a panel is set only by a site administrator.


Restrictions

Project administrators have the following restrictions compared to site administrators:

What Project Admins Cannot Do

Restriction Reason
Set actor (impersonation) The actor decides with whose permissions the panel reads request data for customers - a security-sensitive setting
Edit global or multi-project configurations Configurations that target multiple projects or “All Projects” are managed by site admins only
Access other projects’ configurations Each project admin can only see and manage configurations for their own projects
Manage global module settings Enabling/disabling modules globally affects all projects
Configure delegation policies Delegation settings are a site-level administration function
See audit metadata Audit information (who created/modified, timestamps) is available to site admins only

Configuration Visibility

Visibility and editability are separate. A delegated project admin sees every configuration that can render in their project, including ones they cannot change:

  • Configurations that target their project specifically - visible and editable
  • Configurations targeting “All Projects” (no project filter) - visible, read-only
  • Configurations targeting several projects, one of which is theirs - visible, read-only
  • Configurations that cannot render in their project at all - not visible

Treat this as a disclosure boundary, not just an editing boundary: a global configuration’s name, description and fields are readable by every delegated project admin. Keep anything sensitive in a project-scoped configuration.


Permission Checking

Access Control

  • Site admins: Full access to all configurations
  • Project admins: Only configurations for their projects (if delegation enabled)

Data Access

Project admins cannot set the actor - a panel without an actor reads Jira data as the viewer - and:

  • Users still need Jira permissions to see issue data
  • Panels respect Jira’s Browse Projects permission
  • No elevation of privileges

Next Steps