Hi Atlassian Community,
We have a lot of operational content in Confluence pages that already uses native Confluence tables. Examples are escalation paths, application ownership, internal service directories, and support handoff tables.
The problem is that the editing experience is fine, but once the page is published, those tables become hard to use at scale. We don’t really want to rebuild everything as a Database, because these tables are already embedded in existing documentation and page workflows.
What I’m looking for is an app that can work with the tables we already have and add things like:
Has anyone found a Confluence Cloud app that can upgrade native tables in this way, while still letting teams keep the table inside the page instead of moving the data model elsewhere?
I’d be especially interested in real-world feedback from teams using this for internal operations or service documentation.
Thanks!
Your use case sounds very familiar. If the goal is to keep the existing Confluence tables in place and make them much easier to use after publishing, Simple Table could be worth a look. Full disclosure: I’m part of the team behind it.
What makes it relevant here is that it can work with native Confluence tables through the bodied macro, so you do not have to rebuild everything as a separate database. Based on the requirements you listed, it supports table search, hiding columns, reordering columns, renaming headings, row numbers, and CSV/Excel export.
It can also help with readability when tables get large on the page, since you can control the visible table height and adjust the layout/spacing. For bigger datasets, there is also support for saving the table data as an attachment. One thing to keep in mind is that, in Confluence Cloud, bodied macro changes may not always render fully in editor mode, but you can preview the final result before publishing.
So if your main objective is “keep our existing documentation tables, but make them much more usable for internal operations or service documentation,” this is exactly the kind of scenario where I would test Simple Tables first.
Hope this helps!
Hey @Laurent Van der Velde ,
I agree that native tables are relatively limited...
If you're looking for apps, some of these might be useful:
Now, I'd maybe recommend reaching out to vendors with the list of your requirements for them to confirm if all of that is possible or if there are any workarounds you could use (that's, at least, how I approach it). 👀
Note that I've only tested these a couple of times (I'm not actively using any of them)
If you're still open to using databases (without having to spend too much time), you could maybe check with Rovo if it will be able to transform all that data you have into database elements. It might depend on the actual size of the data, but this could be a much quicker option than manual, APIs, or some other method. 🤔
Hope this helps.
Cheers,
Tobi
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.