Meridian People & Skills Hub reads Jira and Confluence content through its own app user, and that app user sees only what Atlassian's permissions allow it to see. By default that is broad: Every Jira project outside Jira Service Management and every Confluence space is in scope, and there is nothing to add or approve first. This page explains how to keep sensitive projects, spaces, pages, or issues out of scope.
Scoping is done in Atlassian's own permission settings, not in a list inside the app, and the two products work differently. The tasks below are usually done by the person who administers the space or project, so a Confluence space admin or a Jira project admin, in coordination with the global admin who runs the access review.
Set access before you save the profile population mode. Saving the mode is permanent and starts the initial scan straight away, which reads everything then in scope. Restricting content afterwards keeps it out of later scans, but skills already derived from it stay on the profiles. Each person can remove such a skill from their own profile, see Remove a skill.
How access works
-
Confluence. Access is granted per space. The app user has Space Admin on every existing and future space, so it can read them all until you remove that access. A space the app cannot view is skipped silently. You see no error, only fewer results.
-
Jira. Access is role-based and uniform across all projects. The app reaches a project through the project role
atlassian-addons-project-access. Jira Service Management projects are never read, regardless of this role.
Limit access in Confluence
A space admin sets this in Space settings, then Space permissions.
-
Exclude a whole space. Remove the People & Skills Hub app user's view permission from the space. If the space still allows the site's default user group (for example
confluence-users), remove that group's view as well and grant access only to the people or groups who should see the space. Once the app has no way to view the space, it reads nothing from it. -
Exclude a single page. Open the page, add Restrictions, and grant view to only the people or groups who should see it. The app then cannot read that page, even in a space that is otherwise in scope.
Limit access in Jira
A project admin or Jira admin sets this through the project's permission scheme.
-
Exclude a whole project. The app reaches a project through the
atlassian-addons-project-accessproject role, and the members of that role are managed by Atlassian and cannot be edited. To cut the app off, remove that role's grants from the project's permission scheme, or move the project to a permission scheme that does not grant the role (for example, one whereatlassian-addons-project-accesshas no Browse Projects permission). The app can then no longer read the project's issues. -
Exclude single issues. Create an issue security scheme that grants visibility to only the chosen people or groups, apply the scheme to the project, and set the security level on the issues you want to hide. The app cannot read an issue unless its app user is included in that issue's security level.
Confirm the access review
The scan does not start until a global admin confirms that the access is as intended. In Jira, go to Settings, then Apps, then People & Skills Hub.
-
Check the Confluence connection status on the page. If Confluence is not connected, the page links to Atlassian's Manage apps section, where you can connect it. Connecting Confluence is optional, and without it the app derives skills from Jira alone.
-
Set the access in Jira and Confluence as described above, if you need to exclude anything.
-
Tick I have reviewed the content access settings and agree to start skill extraction upon saving.
-
Select the profile population mode and save.
Save configuration stays inactive until you have both confirmed the review and selected a mode. The confirmation is about the review itself: The app asks for it whether or not you changed anything in Atlassian's permission settings, and whether or not Confluence is connected. What happens after you save, and why the choice is permanent, is on Choose a profile population mode.