Skip to end of metadata
Go to start of metadata


To do its work, we need you to grant some permissions for our app. Let us explain, what we need from you.

In Confluence

View Confluence settings

  • We need to retrieve system or instance specific information which include the base url and the cloud ID of your instance.
  • The base url and cloud ID will be used when linking to the admin configuration of our app.

View groups

  • We need to search for users based on the configured group.
  • We are limited by the Confluence Cloud REST API endpoints, which currently do not support a global search without using a specific group.

View user details

  • We need to searches for users in the contact list.

View content details

  • We need to be able to read the information of each user in order for us to map the contact information to the Atlassian users to display the information in the Contacts list.

In User

View active user profile.

  • We need to check whether the currently logged-in user has certain privileges, such as being able to administer groups or access administrator settings.

External domains

Subdomains of atlassian.net

  • In order for us to display profile pictures of each user, we need to be able to access subdomains of "atlassian.net".

Subdomains of gravatar.com

  • In order for us to display avatars of users, with hidden profile pictures , we need to be able to access subdomains of "gravatar.com".

Subdomains of public.atl-paas.net

Why do we do this? What data do we transfer?

Subdomains of wp.com

  • In order for us to display avatars or profile pictures of users, we need to be able to access subdomains of "wp.com", since the images are hosted by WordPress.



This page was last edited on 03/08/2022.