Issue
Users assigned a developer-level role in Fusion are unable to view or edit Solr configuration files (such as solrconfig.xml) or scripts in index and query pipelines. The script editor panel is not visible, even though the role appears to have standard API and UI permissions.
Diagnosis
This issue can occur when the assigned role is missing a required UI permission for certain admin interface components. Checking browser developer tools (network tab) during the attempt may show that API calls to retrieve script editor content are not executed.
If the role already has API permissions equivalent to the default developer role, the missing access is likely tied to a specific GET UI permission path.
Environment
Fusion 5.9.2 and later
Self-hosted deployment on Kubernetes (example: Azure Kubernetes Service)
Applies to any environment where roles and permissions are managed via Fusion Access Control
Cause
The role lacks the GET:/admin/ui-common/** UI permission, which is required to render certain editor components in the Fusion Admin UI. Without this permission, users cannot load the editor view for Solr configurations or scripts.
Resolution
To grant the necessary permission:
In Fusion, go to Access control > Roles.
Select the affected role (for example, a developer role).
Under UI Permissions, add the following entry:
GET:/admin/ui-common/**Save the changes.
Have the affected user log out and log back in to Fusion.
Verify that the script editor or Solr configuration panel now loads correctly.
If the role was recently created or modified, ensure that API permissions match the required baseline for development activities, in addition to the UI permission above.