How are HR teams using Atlassian?
Some people still picture Confluence as a collaboration tool mainly for developers and IT teams. In practice, that is not quite the case. Confluence is used just as widely by non-technical organizations โ HR, marketing, sales, business operations โ to manage policies, guides, onboarding materials and company knowledge.
In HR in particular, everything from hiring to onboarding, internal policy communication and compliance can be run in connection with Atlassian tools.
Attract and Hire. Aligning open roles, managing recruiter bandwidth, keeping the candidate pipeline visible, coordinating interview schedules. This is the stage where a process scattered across spreadsheets moves into real-time dashboards and hiring funnel metrics.
Onboarding. Account and asset provisioning, Day 1 readiness, task assignment, coordination across several teams. Here, manual handoffs between departments turn into automated routing, and resources scattered in different places get organized into a role-based self-service portal.
Compliance and Reporting. Policy documentation with an approval trail, hour tracking, leadership reporting, headcount and budget analysis. This is the stage where policies buried somewhere and the absence of an audit trail become searchable workflows.
Jira, Confluence and Jira Service Management share these three stages between them. Roughly like this:
Jira โ the status of the hiring pipeline and onboarding tasks
Jira Service Management โ receiving and handling employee requests, the self-service portal
Confluence โ HR policies, guidelines, onboarding materials. In other words, knowledge
Ultimately, the goal is that each new tool adds capability rather than complexity โ pulling scattered work into a single HR hub that scales alongside your team. From hiring through compliance, people should be able to find what they need and keep the work moving, all on one platform.
Confluence is a natural fit for that kind of HR hub, or an internal intranet. HR policies, benefits, onboarding materials, workplace guidelines โ the things employees look for most often โ can all live in one place, while each team keeps building out the knowledge it needs in its own space.
In day-to-day operation, though, a different problem tends to surface: there is plenty of content, but employees can't find it.
That's especially true for new hires. The company's structure and the way spaces are organized are still unfamiliar to them, so even when the document already exists, the same questions keep coming back to HR โ "Where do I go for this?", "Which page is that on?"
Building the knowledge and making sure employees can actually reach it, in other words, turn out to be two different problems.
A wiki's freedom is a strength โ and occasionally a burden
One of Confluence's real advantages is that every team can shape its own spaces and page structure around the way it works. IT doesn't have to govern the whole hierarchy for teams to keep building the knowledge they need.
The catch is that a structure which feels obvious to the person who built it may not feel that way to someone arriving for the first time. For a new hire in particular, it's hard to tell where to start, which document to read first, or which space holds the information they're after.
And when a new hire hits that wall, the first thing they do is ask HR.
Situations HR teams run into
First, the onboarding material exists, but "where do I start?" keeps coming up.
You have probably built a solid new-joiner guide page: the org chart, HR policies, benefits, security training, how to use the attendance system. The difficulty is that new hires struggle to keep finding their way back to it. The link you sent by email on day one has already scrolled well out of sight by the second week.
Second, space structures differ by team, so the same instruction doesn't quite land.
You will probably recognize this: "go into your team space and open the onboarding folder" produces a different result in every team. In one team the onboarding page sits near the top, in another it is buried among meeting notes, and in another it has not been created yet. It is an area HR cannot really control directly โ yet when a new hire gets lost, the question still comes to HR.
Third, a good share of first-week questions are "where is that?"
Where do I request annual leave, which version of the expense policy is current, where is the link for mandatory training. These are less questions about content than questions about location. Requests that could have been resolved through self-service end up going to a person, and HR's time goes to searching on someone's behalf rather than to designing the policies themselves.
Maybe what's missing isn't more documents, but a starting point
The usual instinct here is to create one more guide page โ a "read this first" page for new joiners, with all the links gathered in one place.
But that page is also a page you have to go and find. The problem has simply moved one step back.
So it might be worth turning the direction around. Instead of having people go to the documents, what if the menu they need appeared right at the top of the screen, in whichever space they happen to be in? So that employees don't have to remember locations at all.
Designing top menus with onboarding in mind
Flexible Space Navigationย lets you configure the top menu each space needs. When you use it for onboarding, it helps to work through it in steps.
Step 1 โ company-wide menu
The items every employee needs to reach often: HR policies, benefits, internal regulations, mandatory training, attendance and expense systems. This is the step HR defines and maintains directly, and it acts as the single entry point to your policy documents.
Step 2 โ team and role menus
Even within the same company, a new hire in engineering and one in sales need different documents in their first week. Engineering needs development environment setup and code review rules; sales needs product materials and the quoting process.
Flexible Space Navigation lets you configure navigation to match the spaces each team works in, so team members see the menu they need as soon as they enter that space.
This is where it helps most with onboarding. People joining the same team encounter the same menu in the same space, whatever their start date โ which reduces how much the onboarding experience varies by who is handling it or when someone joins.
Stepย 3 โ personal menus
The spaces and documents each employee uses most can differ. Personal navigation can be set up and switched between as needed, so people can move quickly among the menus their own work requires.
It keeps the company-wide structure and the team structure intact while also giving individuals the access paths that suit them.
What changes for the HR team
The onboarding checklist moves from a list of links to something that stays on screen.ย
Unlike a link sent by email, a top menu doesn't disappear. The time it takes for a new hire to become self-sufficient tends to shorten naturally as a result.
You don't have to walk through every location again when someone moves teams.ย
When an employee joins a new team's space, they see the menu that belongs to that space right away. It lets you offer a consistent way in across the whole employee journey, from joining to moving internally.
When a policy is revised, you only update in one place.ย
Point the menu at the current version of the document and everyone sees the same thing, which is what makes managing policy documents against a single reference actually work. Conversations like "I think you're looking at an older version" become rarer too.
Repeat questions go down.ย
When fewer people are asking where things are, HR can spend more time on policies and on people. That is probably the change that matters most.
An easy way to start
Week one โ collect the first-week questions. Ask people who joined recently what they couldn't find, and where, during their first two weeks. Around five people is usually enough for a pattern to appear. That list becomes the first draft of your Step 1 menu.
Week two โ build only Step 1 first. Five to seven company-wide items is plenty. Trying to design a perfect information architecture from the start tends to push the start date further and further out. Put up what people look for most often, and add the rest later.
After that โ run a light pilot with two teams. Teams that hire frequently are a good place to start. Work out the Step 2 menu together with the team lead, then let the next new joiner use it without any separate explanation. Whether "where do I start?" comes up is a natural enough indicator.
Wrapping up
Building an HR hub is usually discussed as a question of adding more tools. But on the Confluence side, the sticking point is less often a missing tool than you might expect. More often, it is that employees can't reach the knowledge you have already built up carefully.
You don't have to give up a wiki's flexibility. Letting each team build knowledge their own way is the right call. It's simply that readers benefit from having one consistent starting point โ especially new hires who are still finding their way around the company.
Giving each space the top menu it needs isn't about creating more documents. It's closer to making the documents you already have visible without anyone having to search for them. For new hires in particular, a small difference like that can change the onboarding experience considerably.
๐ย Flexible Space Navigation
Sources
HR ops collection | Atlassian Marketplace
HR teams | Atlassian
How are HR teams using Atlassian?
Some people still picture Confluence as a collaboration tool mainly for developers and IT teams. In practice, that is not quite the case. Confluence is used just as widely by non-technical organizations โ HR, marketing, sales, business operations โ to manage policies, guides, onboarding materials and company knowledge.
In HR in particular, everything from hiring to onboarding, internal policy communication and compliance can be run in connection with Atlassian tools.
Attract and Hire. Aligning open roles, managing recruiter bandwidth, keeping the candidate pipeline visible, coordinating interview schedules. This is the stage where a process scattered across spreadsheets moves into real-time dashboards and hiring funnel metrics.
Onboarding. Account and asset provisioning, Day 1 readiness, task assignment, coordination across several teams. Here, manual handoffs between departments turn into automated routing, and resources scattered in different places get organized into a role-based self-service portal.
Compliance and Reporting. Policy documentation with an approval trail, hour tracking, leadership reporting, headcount and budget analysis. This is the stage where policies buried somewhere and the absence of an audit trail become searchable workflows.
Jira, Confluence and Jira Service Management share these three stages between them. Roughly like this:
Jira โ the status of the hiring pipeline and onboarding tasks
Jira Service Management โ receiving and handling employee requests, the self-service portal
Confluence โ HR policies, guidelines, onboarding materials. In other words, knowledge
Ultimately, the goal is that each new tool adds capability rather than complexity โ pulling scattered work into a single HR hub that scales alongside your team. From hiring through compliance, people should be able to find what they need and keep the work moving, all on one platform.
Confluence is a natural fit for that kind of HR hub, or an internal intranet. HR policies, benefits, onboarding materials, workplace guidelines โ the things employees look for most often โ can all live in one place, while each team keeps building out the knowledge it needs in its own space.
In day-to-day operation, though, a different problem tends to surface: there is plenty of content, but employees can't find it.
That's especially true for new hires. The company's structure and the way spaces are organized are still unfamiliar to them, so even when the document already exists, the same questions keep coming back to HR โ "Where do I go for this?", "Which page is that on?"
Building the knowledge and making sure employees can actually reach it, in other words, turn out to be two different problems.
A wiki's freedom is a strength โ and occasionally a burden
One of Confluence's real advantages is that every team can shape its own spaces and page structure around the way it works. IT doesn't have to govern the whole hierarchy for teams to keep building the knowledge they need.
The catch is that a structure which feels obvious to the person who built it may not feel that way to someone arriving for the first time. For a new hire in particular, it's hard to tell where to start, which document to read first, or which space holds the information they're after.
And when a new hire hits that wall, the first thing they do is ask HR.
Situations HR teams run into
First, the onboarding material exists, but "where do I start?" keeps coming up.
You have probably built a solid new-joiner guide page: the org chart, HR policies, benefits, security training, how to use the attendance system. The difficulty is that new hires struggle to keep finding their way back to it. The link you sent by email on day one has already scrolled well out of sight by the second week.
Second, space structures differ by team, so the same instruction doesn't quite land.
You will probably recognize this: "go into your team space and open the onboarding folder" produces a different result in every team. In one team the onboarding page sits near the top, in another it is buried among meeting notes, and in another it has not been created yet. It is an area HR cannot really control directly โ yet when a new hire gets lost, the question still comes to HR.
Third, a good share of first-week questions are "where is that?"
Where do I request annual leave, which version of the expense policy is current, where is the link for mandatory training. These are less questions about content than questions about location. Requests that could have been resolved through self-service end up going to a person, and HR's time goes to searching on someone's behalf rather than to designing the policies themselves.
Maybe what's missing isn't more documents, but a starting point
The usual instinct here is to create one more guide page โ a "read this first" page for new joiners, with all the links gathered in one place.
But that page is also a page you have to go and find. The problem has simply moved one step back.
So it might be worth turning the direction around. Instead of having people go to the documents, what if the menu they need appeared right at the top of the screen, in whichever space they happen to be in? So that employees don't have to remember locations at all.
Designing top menus with onboarding in mind
Flexible Space Navigationย lets you configure the top menu each space needs. When you use it for onboarding, it helps to work through it in steps.
Step 1 โ company-wide menu
The items every employee needs to reach often: HR policies, benefits, internal regulations, mandatory training, attendance and expense systems. This is the step HR defines and maintains directly, and it acts as the single entry point to your policy documents.
Step 2 โ team and role menus
Even within the same company, a new hire in engineering and one in sales need different documents in their first week. Engineering needs development environment setup and code review rules; sales needs product materials and the quoting process.
Flexible Space Navigation lets you configure navigation to match the spaces each team works in, so team members see the menu they need as soon as they enter that space.
This is where it helps most with onboarding. People joining the same team encounter the same menu in the same space, whatever their start date โ which reduces how much the onboarding experience varies by who is handling it or when someone joins.
Stepย 3 โ personal menus
The spaces and documents each employee uses most can differ. Personal navigation can be set up and switched between as needed, so people can move quickly among the menus their own work requires.
It keeps the company-wide structure and the team structure intact while also giving individuals the access paths that suit them.
What changes for the HR team
The onboarding checklist moves from a list of links to something that stays on screen.ย
Unlike a link sent by email, a top menu doesn't disappear. The time it takes for a new hire to become self-sufficient tends to shorten naturally as a result.
You don't have to walk through every location again when someone moves teams.ย
When an employee joins a new team's space, they see the menu that belongs to that space right away. It lets you offer a consistent way in across the whole employee journey, from joining to moving internally.
When a policy is revised, you only update in one place.ย
Point the menu at the current version of the document and everyone sees the same thing, which is what makes managing policy documents against a single reference actually work. Conversations like "I think you're looking at an older version" become rarer too.
Repeat questions go down.ย
When fewer people are asking where things are, HR can spend more time on policies and on people. That is probably the change that matters most.
An easy way to start
Week one โ collect the first-week questions. Ask people who joined recently what they couldn't find, and where, during their first two weeks. Around five people is usually enough for a pattern to appear. That list becomes the first draft of your Step 1 menu.
Week two โ build only Step 1 first. Five to seven company-wide items is plenty. Trying to design a perfect information architecture from the start tends to push the start date further and further out. Put up what people look for most often, and add the rest later.
After that โ run a light pilot with two teams. Teams that hire frequently are a good place to start. Work out the Step 2 menu together with the team lead, then let the next new joiner use it without any separate explanation. Whether "where do I start?" comes up is a natural enough indicator.
Wrapping up
Building an HR hub is usually discussed as a question of adding more tools. But on the Confluence side, the sticking point is less often a missing tool than you might expect. More often, it is that employees can't reach the knowledge you have already built up carefully.
You don't have to give up a wiki's flexibility. Letting each team build knowledge their own way is the right call. It's simply that readers benefit from having one consistent starting point โ especially new hires who are still finding their way around the company.
Giving each space the top menu it needs isn't about creating more documents. It's closer to making the documents you already have visible without anyone having to search for them. For new hires in particular, a small difference like that can change the onboarding experience considerably.
๐ย Flexible Space Navigation
Sources
HR ops collection | Atlassian Marketplace
HR teams | Atlassian