Summary

In Automation for Confluence, the “Grant space permissions” action currently only allows selecting users and groups via the UI picker. There is no option to use smart values to dynamically supply the user or group to whom permissions should be granted.
This restricts the ability to build dynamic, reusable rules where the target user/group is determined at run time (for example, based on webhook payloads, form inputs, or other context in the rule).
 

Problem / Current Limitation

• The user/group field in the “Grant space permissions” action only supports static selection from the user and group picker.
• There is no support for smart values (e.g., {}{{{{webhook.userEmail}}{}}}, {}{{{{issue.reporter.displayName}}{}}}, {}{{{{rule.actor}}{}}}) for user or group selection.
• As a result:
  • Rules cannot easily grant space permissions to different users/groups per execution.
  • Use cases like “grant space permissions to the user who submitted this request” or “add the requester’s group” require complex workarounds

Suggested Implementation 

Introduce Smart Value Support in User/Group Fields

• Allow the user and group selectors in the “Grant space permissions” action to accept smart values as an alternative to the static picker.
• Examples of supported smart values:
  • User: email, accountId, or username (depending on internal representation)
  • Group: group name or group ID
• Allow combining static entries and smart values if technically feasible.

Workaround

As a workaround, admins must use the “Add space permissions” REST API via other actions:

• The API only supports one user/group and one permission set at a time, making it cumbersome.
• Complex rules require multiple API calls and extra logic, which is error-prone and hard to maintain.