I am trying to think of ways that our HR team can make information more accessible to employees and to leaders (team leads and team captains). We currently have multiple systems that are used for different processes (ATS + LMS, HRIS, external blog for resources) and they have mentioned some frustration. Especially for the hiring process.
What are some examples of what you have done/seen? Any ideas to help me automate and make lives easier?
Greetings and welcome @Cat Tinsley to the Atlassian Community!
A few teams use Confluence as a central HR hub by creating dedicated spaces for onboarding, policies, job postings, and team resources and linking everything from a single landing page so employees don't have to hunt across systems. Natively, Confluence Cloud gives you Blog posts for announcements, Spaces for organizing HR content by topic or department, and (on Premium/Enterprise) Company Hub as a centralized entry point.
That gets you reasonably far, but the native experience is fairly...how can we say...flat: no news scheduling, no polls or social interaction, no events calendar, and no way to track whether employees have actually read important policy updates.
If you want to go further and genuinely replace or complement that external blog and give HR a more engaging employee-facing experience inside Confluence, it might be worth looking at Mantra. And just in full disclosure, I'm with Aura Apps, the team behind it.
Mantra sits on top of Confluence Cloud and adds the kind of features that make it feel more like an intranet than a wiki: drag-and-drop dashboards that HR can manage without IT help, a news editor with scheduled publishing and mandatory reads (useful for policy rollouts where you need to confirm acknowledgment), communities for things like onboarding cohorts or hiring manager resources, a people directory with custom fields, and a native mobile app with push notifications for reaching frontline or remote employees.
For the hiring process specifically, you could build a dedicated hiring manager community with its own dashboard ... quick links to your ATS, guides for interviewers, templates for feedback, and a feed of relevant updates. As a result, leaders have one place to go instead of bouncing between systems.
The mandatory reads feature in particular tends to resonate with HR teams who need to ensure employees have seen a policy change or compliance document, since it tracks who has and hasn't read something.
Let me know if you have questions about any of this, as there are a few different ways to structure it depending on how much of your HR content you want to migrate into Confluence versus just link to from there. You can schedule a demo any time if you like with us for a walkthrough.
Thanks, best of luck, and again, welcome!
Joshua
Content Writer & US Representative
Aura Apps and Agile Hive (products of Seibert Group GmbH)
Hi @Cat Tinsley, welcome to the community, you're in the right place! :)
I see how having that multi system can create frustration internally.
A few things that tend to help:
1. Create a single "go-to" space for HR information:
Rather than asking people to remember which system holds what, build one central space in Confluence that acts as the directory (you can add clear sections for employees vs. leaders, with direct links to the relevant tool for each task). The goal is that nobody has to guess where to go.
2. Tackle the hiring process first
Since that's where the most frustration is, mapping out the full hiring lifecycle in one place (you can also use whiteboards with stages, owners, next steps, and links to your ATS at each point). Just to try give team leads a reliable reference to reduces back-and-forth with HR. Checklists work especially well here too.
3. Standardise pages from the start with page presets
To battle the scary 'blank space syndrome', we built a feature in Mosaic to define exactly which pages get created automatically (and in bulk!) when a new space is set up. Every hiring manager or team lead starts with the right structure already in place, rather than building from scratch each time. On top of that, and to help with the blank page syndrome you can then apply Confluence templates from that same dash. I've tried make a quick video here.
For some other practical starting points to go with what the others have already shared, we've put together a few HR resources worth browsing:
- HR blog posts on workflows and knowledge management
- Confluence HR templates ready to adapt
- Enterprise collaboration guide for structuring your spaces
Hope that helps! happy to go deeper on any of these if you need a hand.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Daniel_Domene_Kolekti !
Thank you so much for response and help! These are definitely a great place to start.
I do have some additional questions and would appreciate any additional advice/resources if you have ideas:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello and welcome to Atlassian Community@Cat Tinsley
Think of Confluence as the "front door" for HR knowledge, not a replacement for your ATS, HRIS, or LMS. Use it to host employee and leader hubs for policies, workflows, and checklists, while keeping sensitive personal data securely inside your core systems. Simply map the hiring lifecycle on dedicated pages that clarify step ownership and link directly to where the actual work occurs.
With Confluence Premium, you can use automation for routine tasks and Rovo for smart searching, just ensure your space permissions are tightly locked down (especially for HR, you don't want, Really don't want anybody else see that).
To solve the friction quickly, start by mapping a single leader-facing guide with clear handoffs, then iterate based on feedback from your next few hires.
Best,
Arkadiusz🤠😎
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Arkadiusz Wroblewski !
Thank you so much for response and help!
I do have some additional questions and would appreciate any additional advice/resources if you have ideas:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cat Tinsley 👋🏻
First of all, welcome to community! ✨
And as @Arkadiusz Wroblewski mentioned, I agree to all the points mentioned.
I would just like to add that you can also leverage the below Atlassian's links to structure your workspace.
I hope this answers your question. 🙂
Thanks,
Anwesha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anwesha Pan
Thank you for the warm welcome and for the hand. I appreciate the help and suggested resources. 😊
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Cat Tinsley ,
The multi-system frustration you're describing is really common, and Confluence can do a lot of the connective tissue work here, even if it doesn't fully replace your ATS or HRIS.
A few things that have worked well for our HR team in this situation:
Start with structure before content. The instinct is usually to start migrating content, but the more useful first step is deciding who needs what. Separate spaces for HR-internal content (incident records, personnel files) vs. employee-facing content (policies, benefits, onboarding) keeps permissions clean and makes navigation much less confusing. A dedicated onboarding space for new hires specifically tends to reduce the "where do I find this?" questions significantly.
Make Confluence the front door, not a replacement. For the hiring process specifically, you don't need to move everything out of your ATS; you just need one reliable place for hiring managers to orient themselves. A hiring manager hub page with a clear checklist for each stage, links to the ATS at the right moments, interview templates, and feedback guidelines can remove a lot of the back-and-forth with HR. Checklists (either native or via a Jira Checklists integration) work especially well here.
For tracking and visibility across processes, this is where we've seen Table Filter, Charts & Spreadsheets for Confluence (the app we make at Stiltsoft) come in handy for HR teams. If you're maintaining things like headcount tables, onboarding progress trackers, or any kind of structured data in Confluence pages, Table Filter, Charts & Spreadsheets lets you slice and filter that data without leaving Confluence. So a team lead can quickly see "show me only open roles in my department," or HR can filter a benefits eligibility table without needing to export to a spreadsheet. It's not an HRIS replacement, but for the data that does live in Confluence, it keeps things navigable as the tables grow.
Templates save more time than you'd expect. Confluence's built-in HR templates (90-day plan, job description, quarterly check-in) are a solid starting point.
One thing worth flagging: whatever structure you set up, use space analytics periodically to see what content people actually visit. HR spaces often have pages that nobody reads, and that's useful signal for where the information design needs work.
Hope this helps! Let me know if you have any questions :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.