What is a correct method to target specific user groups with an Application Link?

What is a correct method to target specific user groups with an Application Link?

• A. Add the app link in a space and grant access via a group or individual user
• B. Create an app link per repository
• C. Limit access to admin users only
• D. Use a global access token

Answer: (A)

Targeting specific user groups with an Application Link is best done by placing the app link inside a space and granting access to that space to the desired groups or individual users. This leverages Confluence’s permission model, so only people who have space access can see and use the external application connection. It provides granular, scalable control—you can assign or remove users or groups from the space as needs change. Creating an app link per repository doesn’t map to Confluence’s access model and would complicate management. Limiting access to admin users only is overly restrictive and unnecessary when you can precisely define who should access the integration. Relying on a global access token bypasses user-level permissions and is insecure, as it would grant access regardless of who the user is.

Targeting specific user groups with an Application Link is best done by placing the app link inside a space and granting access to that space to the desired groups or individual users. This leverages Confluence’s permission model, so only people who have space access can see and use the external application connection. It provides granular, scalable control—you can assign or remove users or groups from the space as needs change. Creating an app link per repository doesn’t map to Confluence’s access model and would complicate management. Limiting access to admin users only is overly restrictive and unnecessary when you can precisely define who should access the integration. Relying on a global access token bypasses user-level permissions and is insecure, as it would grant access regardless of who the user is.