Database associations

[dvaughn]

I am trying to create a project reporting hierarchy within Confluence where items can be associated with (and thus reported in) more than one database as can be done in notion.  Has anyone successfully done this? If so how.  Thanks

[Himanshu Tiwary]

Hi @dvaughn ,

Yes, you can do this to a point in Confluence by linking items between databases, so one project can be connected to risks, benefits, teams, or other records in separate databases.

The limitation is that Confluence does not work as deeply as Notion for multi-database relationships and reporting. So you can create the associations, but the reporting and rollup side is still more limited.

The usual approach is to keep one main database, such as Projects, and then link each item to entries in other databases like Risks or Benefits. That works well for structure and visibility, but if you need more advanced reporting, Confluence may feel limited.

So the short answer is yes, partially possible, but not as flexible as Notion.

If this helped, I’d really appreciate a Kudos.

[dvaughn]

Thanks for the suggestions.  As you pointed out, we seemed to have run up against that limitation.  We can't get past those for some of our advanced reporting scenarios.  Hopefully those improvements are on a short-term roadmap.  

[Himanshu Tiwary]

 For sure, and also if you find it helpful can you please give me a recognition in my profile as it will help me a lot :)

[kh-federico]

Hi @dvaughn , we noticed you posted this in multiple places across the forums, which is against our Rules of Engagement. We’ve kept this one live - if you prefer for your content to remain in a different group or collection, please let us know via the “report to moderators” function and we’d be happy to move it for you. Please also take a moment to review our rules so you're aware for next time. Thanks!

[Anwesha Pan]

Hi @dvaughn 👋🏻 

Great question — this is one of the most common pain points for teams migrating from Notion to Confluence. The short answer is that Confluence databases do not currently have a native "Relation" field type like Notion does, so you can't natively link an entry in Database A to entries in Database B with bidirectional references and rollups.

That said, here are the practical approaches to approximate this. Based on current Confluence database capabilities, you have a few building blocks to work with:

1. Embed the same database in multiple places — A single database can be embedded (via /embed database or by pasting its URL) on any number of Confluence pages. Each embed can use a different view with its own filters, sorts, and visible fields. This means one master database can appear in multiple reporting contexts showing only the relevant slice of data.

2. Use a "Tags" or "Multi-select" field as a category marker — Add a multi-select field like "Reports To" or "Program" where each entry can be tagged with multiple categories (e.g., "Program Alpha", "Q3 Release", "Platform Team"). Then create filtered views per category. This gives you the "item belongs to multiple groups" behavior.

3. Page Link field type — Confluence database entries can link to Confluence pages. If your hierarchy items are pages, you can reference them from multiple database entries.

Alternatively you can use Jira as the Relational Layer and Confluence for reporting:

• Use Jira labels, components, or custom fields to tag items across multiple programs/workstreams

• Use Jira filters/JQL to create the reporting slices

• Embed Jira filters or dashboards into Confluence pages via Smart Links

• This gives you true multi-dimensional reporting with Jira's richer filtering, and items naturally belong to multiple categories

Hope this answers your question. 🙂

Thanks,
Anwesha