You know this moment. A meeting starts in five minutes, you open the shared folder to grab the latest version of a document, and you find six versions with names like final, final-v2, and final-USE-THIS. Or you upload a file, feeling productive, only to discover a colleague uploaded the same thing two minutes ago. Klaida Sulko has a name for that scramble, and she built a whole Work Evolution Summit session around ending it.
Klaida is a product marketing manager at Elevatic and her talk tackled a gap most teams have simply learned to live with. Your work runs across three platforms that do not talk to each other, and the seam between them costs you time every single day. Her argument is that you can close that seam without moving or duplicating a single document.
Three Platforms, No Connection
Start by naming where your work actually lives. You plan and execute tasks in Jira. You capture knowledge and decisions in Confluence. And your governed company documents sit in SharePoint, where compliance and control already live. Three solid pillars, and no connection between them.
That disconnection is where the friction hides. You lose time hunting for the current version of a file. You upload duplicates because you cannot see what already exists. Versions multiply, and information settles into silos that nobody can see across.
The daily document hunt
Klaida asked the room how many people had searched for the latest version of a file right before a meeting and drowned in copies, and the hands told the story. Once you have a name for the pattern, you start noticing how much of your week it quietly eats.
Teamwork Collection Helps, and a Gap Remains
Atlassian has an answer for part of this, and Klaida gave it full credit. The Teamwork Collection pulls the pieces together. Jira plans and tracks the work, Confluence brings documentation and knowledge into one place, Loom handles fast communication, and Rovo adds AI and context across the flow. Together they give you one workflow with shared context, which leads to better decisions.
Then she pointed at what the collection still leaves open. Your workflows and your documents remain disconnected. The work happens in Jira and Confluence, the documents keep living in SharePoint, and you end up duplicating content and switching from one system to another to get anything done. The collaboration got better. The document layer stayed on the other side of a wall.
Three Best Practices to Close the Gap
Klaida structured her fix as three practices you can hold onto, whatever tooling you choose.
Keep knowledge unified by bringing SharePoint content into Confluence. When your team can see SharePoint’s document structure in the Confluence sidebar and work with it there, nobody has to leave the page to find a file.
Keep workloads connected by bringing SharePoint items onto Jira issues. Attach the right documents to the work itself and your tasks carry the context people need, which turns ordinary tickets into genuinely document-driven processes.
Keep governance in SharePoint. This is the one Klaida would not bend on. SharePoint stays your single source of truth, so you stop duplicating files, stop scattering information into silos, and stop paying the switching tax. The documents never move. Only the access to them travels to where the work happens.
To deliver those three, Elevatic built its Meridian documents integration for Atlassian, which connects SharePoint with both Jira and Confluence and pulls documents into the workflow while the originals stay governed in SharePoint. Klaida summed up the whole philosophy in one line.
“we don’t move your documents, we connect them to where work happens”
What It Looks Like in Practice
Klaida grounded the idea in everyday scenarios rather than abstractions. A marketing team plans a campaign in Confluence and tracks the tasks in Jira, with all the related SharePoint content reachable from the Confluence sidebar. One person stores the marketing assets in SharePoint and links the cost breakdown straight into the Jira issue from there. They embed the file in the Confluence page and update it in place, and a colleague reviews the updated file directly from Jira and approves it. Everyone works from the current version, and the plan moves.
An HR team runs event approvals the same way. Someone opens a Jira approval issue for the budget and links the cost sheets to the task. A teammate updates the sheet from Confluence, and the whole team executes against up-to-date files with no email attachments flying around.
The procurement example went furthest. For fleet management processes documented in Confluence, the team browses the SharePoint folder structure in the sidebar, embeds files and folders into the process pages, and opens or edits documents in the browser with every change synced back. An assistant for SharePoint gives them an overview of every file linked into a page. Upload a new file from inside Confluence and it lands in SharePoint too. On the Jira side, a project admin can connect SharePoint folders to a project so that the right folder attaches automatically to each new task. Edit from Jira or from Confluence, and the latest version follows you everywhere.
The Question Everyone Asks: Who Can See What?
The moment you connect systems, the security questions arrive, and the audience did not hold back. The first one was about access. If you invite partners into Confluence with user-based access, and SharePoint controls access per file, what happens in between?
“permissions stay intact”
Klaida was firm on this. The integration rides on SharePoint’s own permission scheme. If you can see a file in SharePoint, you can reach it from Confluence and Jira. If you cannot, you get a message telling you to contact your administrator, with no override and no super-user shortcut. A follow-up pressed further. Can someone without rights at least see the file name, since a confidential campaign title could itself leak something? Her answer was no. You see nothing about the file or folder, only the message to talk to your admin. As the host joked, that is what naming conventions like Secret Project Pineapple are for.
Klaida was also honest about what the tool does not do yet. Asked whether it could stop someone from attaching a wrongly classified or confidential document, or respect SharePoint sensitivity labels, she said not currently, and welcomed the idea as something worth building. That candor matters more than a polished feature list when you are deciding whether to trust a vendor with your governance.
From a Thousand Pages to the One That Matters
The sharpest challenge came from someone at a 5,000-person institution, who reframed the whole problem. For a large organization, the hard part is not attaching a document to a workflow. It is what sits inside that document and how it maps to the task. Picture a thousand-page document where only page 854 is relevant to the work in front of you. How do you point straight to it?
Klaida’s answer today is a pager that lets you select a specific page or slide, so you can jump to slide 15 of a deck or the right page of a long file rather than scrolling for it. She was open that this is where AI comes in next, extracting and surfacing the relevant content automatically, and that the team is exploring it actively. It is a fair marker of where document-driven work is heading. Connecting the file to the task is step one. Connecting the task to the exact part of the file that matters is the frontier.
The thread running through Klaida’s session is worth carrying back to your own stack. Every tool you add promises to unify your work, and each one quietly becomes another place to look. So ask yourself the honest question before you adopt the next one. Are you giving your teams a single source of truth, or just one more silo with a nicer interface?
—
About Life in Codes
Life in Codes is on a mission: to support organizations of all kinds to work in a more productive way. That means smart tools, healthy practices, and training the people. As an Atlassian Solutions Partner active in Romania, Estonia, Belgium, UK and the UAE, with our team spread across Europe.
Our client roster includes start-ups, SMEs, large financial institutions like SWIFT, government organizations like the European Commission, and logistics providers such as DHL.Our expertise spans a wide range of solutions, including ITSM, Agile Project Management, Digitalization, Knowledge Management, next-level customer support, DevOps, cloud migration and Rovo AI agents.
We firmly believe that working smart is universal – regardless of industry, company size, or team composition. – our diverse client base is a testament to this philosophy. Whether you’re a tech-focused team or not, Atlassian tools, coupled with our expertise, can significantly enhance your productivity and collaboration.
At the end of the day, we believe in the power of teamwork and we aspire to help people reach their full potential. By partnering with Life in Codes, you’re not just adopting new tools – you’re embracing a more efficient, collaborative, and successful way of working. Schedule an appointment
