Hello Atlassian Community!
Confluence Cloud is evolving fast, and Databases might be the most powerful feature you’re not using yet. Whether you’re managing product features or pasta ingredients (yes, really), Confluence Databases offer a structured-yet-flexible way to organize, connect, and surface data across your workspace.
In this article, I’ll introduce how Databases work in the Cloud, why they matter, and share an example that made the concept click for my users, through the universal language of food.
What are Confluence Databases?
Think of Confluence Databases as smart tables that live in your space but can be reused, linked, and embedded across multiple pages, and even within each other.
They allow you to:
- Create fields with rich data types (status, people, page, date, media, and more)
- Relate entries between databases
- Filter and sort data like a spreadsheet
- View data in table, card or board format
- Maintain a single source of truth across your content
Real-World Use Case: Recipes and Ingredients
When introducing Databases to our teams, I skipped the tech jargon and jumped straight into something universal: food.
I created two databases:
- Recipes: Fields included cuisine, cook time, Region it belonged to, type and cost.
- Ingredients: Each row listed an ingredient, spice level, and a picture of it.
Then I linked each recipe entry to its list of ingredients.
This helped users instantly understand how databases could:
- Show relationships
- Be reused across pages
- Make information easier to update and consume
And as a fun twist, it sparked team conversations about dishes from around the world. From dumplings to dal, ramen to ravioli, people shared their own favorites while learning how databases work.
Features You Should Explore
- Linked Databases: Reference entries from one database inside another (like “lookup fields”)
- Views: Create table, board, or card views to present data differently
- Inline Filters: Let viewers filter by dropdowns without editing the page
- Smart Fields: Use people, page, status, and more for structured inputs
These features turn a basic table into a living knowledge hub.
From Pasta to Product Plans: Why Databases Stick
Databases aren’t just for PMs and project managers, they’re for everyone who works with evolving, interlinked content. Start small. Even if you begin with recipes, you’ll soon see how this feature can transform how your team collaborates and documents.
Stay tuned, in the next article, I’ll explore how to build your first linked database system from scratch, and a few more favorite dishes on the side. 😊
