Problem
Currently all published parameters are designed to be exposed to users when workspaces are deployed through Workspace Apps. And when I add a parameter for admins and publish the workspace again for existing apps, the new parameter is shown in workspace apps by default, needing to uncheck ‘show in app’ for each corresponding app.
In many cases, authors require parameters that:
- Need configuration per app
- Must remain editable by Flow administrators
- Should not be exposed to end users
This creates a conflict between deployment configuration and user-facing input.
Proposed Enhancement
Add a property on published parameters in Workbench such as:
Visible in Flow Apps:
☑ Yes
☐ No
or
Parameter Scope:
- User Input
- Administrator Configuration
Example Use Case
A workspace contains:
- End-user parameters (file uploads, project selection, dates)
- Administrative parameters (resource paths, API endpoints, queue names, environment settings)
Administrators need to configure the latter when creating Workspace Apps, but end users should never see or modify them.
Benefits
- Cleaner user interfaces
- Improved security
- Better separation between configuration and input
- Reduced risk of user error
- Faster Workspace App deployment
Expected Behaviour
The parameter remains:
- Published
- Available during deployment and app configuration
- Available through automation and API execution
But is hidden from Workspace App end users.