Managing Flow App Permissions in FME Flow 2026.1 or Newer

Tim Shin
Tim Shin
  • Updated

Introduction

In FME Flow version 2025.2.x or earlier, Resource and Connection permissions for Flow Apps were granted access via their associated API tokens.

As of FME Flow 2026.1, Flow App API token dependencies are being removed and replaced by a tokenless model. Flow App permissions will no longer be configured through token permissions; instead, they will be secured via a Flow App Identifier. This change means that Flow App permissions will now be tied to the app owner. These permissions will be chosen by the user when creating the Flow App. This will affect all Flow Apps (Workspace Apps, Automation Apps, AR Apps, and Gallery Apps). 

This allows Flow Apps to be run or displayed without requiring an exposed API token. This change was made to enhance protection against token misuse and align security practices with current best practices in API security. 

Requirements

  • FME Flow 2026.1 or newer
  • If restoring a backup created or importing a project from an FME Flow instance older than 2026.1.x: configuration file (.fsconfig) or Project file (.fsproject) from version 2025.2.x or earlier 

 

Adding Flow App Resource and Connection Permissions

In FME Flow versions 2025.2.x and older, Flow App permissions were set via API tokens:  

 

Flow App Connections token permissions in 2025.2.x

 

Flow App Resources token permissions in 2025.2.x

These permissions will now be set through the Resource/Connection Permissions tabs when creating or editing a Flow App. In Workspace Apps, Resource/Connection Permissions will only appear when the workspace being used contains file parameters (for Resource Permissions) or Published/Mixed Connection dependencies (for Connection Permissions).

 

Adding Resource Permissions 

1. Add Resource Permission

To add Resource Permissions to a Flow App containing file parameters, click on the Resource Permissions tab when creating or editing a Flow App to expand the drop-down and click on the Add Resources button.

 

2. Select Resource

In the Select file for pop-up menu, select the resource folder you want the Flow App to have permissions to, and click Confirm.

 

3. Check Resource Permission

You will now see the resource folder added as a Resource Permission.

 

Adding Connection Permissions

1. Add Connection

To add Connection Permissions to a Flow App containing Published or Mixed connections, click on the Connection Permissions tab when creating or editing a Flow App to expand the drop-down and click on the Add Connections button.

 

2. Select Connections

In the Add Connections pop-up menu, you can filter by Connection Type using the Connection Type filter located in the top-left of the menu. Select which connection you want the Flow App to have permissions to, and click Add Connections.

 

3. Check Connection Permissions

You will now see the Connections added as Connection Permissions. 

 

Migrating Flow App Permissions Through a System Restore or Project Import

Flow App token permissions can be transferred in two ways: by performing a Backup and Restore, or by importing a Project containing Flow Apps in FME Flow 2026.1.x or later from an older version of Flow. Previously granted Flow App Resource and Connections token permissions will be logged in the Backup and Restore History, Projects History, and as a Task log

Only Connection Flow App token permissions will be transferred to the Flow App. Resource Permissions will not be migrated over. Migrated Flow Apps with file parameters will continue to work as they did in older versions (2025.2.x or earlier) of Flow, but any modifications or additions to Resource Permissions must be performed manually (See Adding Resource Permissions). 

Viewing Log Files After a System Restore or Project Import

To view the log after a System Restore or Project Import, click View Details after System Restore or Project Import completes.

 

The logs will show that previously granted Connection token permissions are added and associated with the Flow App name rather than an API token. You can see that the shared resource permissions are ignored and will not be transferred over.

 

On the restored Flow Apps Edit page, if you click the Connection Permissions drop-down, you will see that the token permissions have been transferred.

Additional Resources

Getting Started with FME Flow Apps

Flow Apps Documentation

Authorization in the FME Flow REST API | Token Management

Managing Security Tokens

Creating Parameters and Uploading Data for Self-Serve Access

Published Parameters in FME Form

 

Was this article helpful?

We're sorry to hear that.

Please tell us why.

As of January 14th, 2026, comments on knowledge base articles have been closed. To make sure questions don’t get missed and to enable more community support, we’ve moved discussions to the FME Community. If you have a question or a comment about this article, please create a new post or create a support ticket.