Hi Support Team,
We are currently exploring the possibility of developing a custom plugin for Confluence Cloud to help us identify and archive unused spaces. Specifically, those that have not been updated or accessed in the last two years. As of now, we understand that there is no built-in feature in Confluence Cloud that directly supports automatic space archival based on activity history.
To move forward with this solution, we have a few questions regarding custom plugin development and data storage:
If we develop this plugin using Forge, can we store data (e.g., space metadata, access logs, archive status) using Atlassian’s infrastructure?
Are there any limitations to the amount or type of data that can be stored using Forge Storage API?
In case we need to store and process larger datasets (such as usage statistics or audit trails), would we be expected to use our own external storage?
Would using the Connect framework offer more flexibility for data storage in such a use case?
We’d appreciate your guidance on best practices and available options for plugin data management within the Atlassian Cloud environment.
Thank you in advance for your support. We look forward to your advice on how best to approach this.
Br,
Raj