Stop Using Page Properties. Confluence Databases + Rovo Are Better

[#1]

Page Properties Reports break when people forget to add the macro. You chase teams for updates. Reports go stale.

Confluence Databases fix this. Rovo makes them powerful.

What we built: Team Tools Directory

Create a Database in Confluence. Columns: Tool name, Owner, Cost per year, Renewal date, Status.
Set Status as Single select: Active, Renewal soon, Cancelled.
Share the Database link. No macro needed. Teams update it because it’s one table.
Then let Rovo reason on it
Prompt: Read the Team Tools Database. Find all tools where Status equals Active and Renewal date is before next 60 days. Create a table with Tool name, Owner, Cost. Then draft an email to each Owner.

Rovo does in 30 seconds what used to take 3 hours.

Result
We cut SaaS spend 18 percent in one quarter. No more stale Page Properties. No more “who owns this tool” Slack threads.

Tip
Add a Last reviewed date column. Make a Database view filtered to Last reviewed is before 90 days ago. Now you have an auto-expiring inventory.

Are you still on Page Properties? What’s stopping you from switching to Databases?

[Rob Hean]

ohh, nice solution!

Only difference with Content Properties (new name for "page properties") is that it lives on a Page/Live Doc/Blog, so you'd be able to add more info or context to that vs. a Database that wouldn't contain the same type of info. e.g. if I'm using it on a page that also describes the background of the product, why we chose to use it, etc. that would be hard to have on a database.

Also thinking about groups that can't use Rovo - We could still provide the various views by renewal/update date, but would just lose the email generation.

Also curious your thoughts on making this an agent and then automating it? e.g. run once a week and grab any group with the renewal date in the next 60 days?

[Dave Mathijs]

Hi @HEMANT SAINI At launch, I was very excited about Confluence Databases. For me, it was the missing piece where Notion databases and properties shine.

However, since its inception, I've found the use of database to be very 'slow'. Too much white space, too much clicks, no relationships between properties. Also, it still doesn't really add metadata or custom fields to pages or live docs.