I would like to raise a formal objection regarding the removal or planned removal of the functionality that allows users to view and access files attached to Confluence Cloud pages.
The attachments uploaded to Confluence Cloud are not the property of Atlassian. They are user content and, in many cases, business-critical customer data owned or controlled by the customer. Atlassian provides a cloud service for storing, managing, and accessing this content, but that does not give Atlassian the right to materially restrict access to such content merely on the basis of simplifying the user interface.
From a legal and contractual perspective, restricting access to customer-owned attachments may interfere with the customer’s legitimate right to access, use, retrieve, and manage their own data. A user interface change must not result in a practical limitation on access to customer content, especially where that content was uploaded under the reasonable expectation that it would remain accessible through the product.
If Atlassian intends to change how attachments are displayed, it should provide an equivalent, clear, and reliable alternative method for accessing all attachments associated with a page. Any design simplification must preserve the customer’s ability to locate, view, download, audit, and manage their own files without unnecessary burden or loss of functionality.
I therefore object to any removal of attachment visibility or access functionality that limits customers’ practical ability to access their own uploaded files. I request that Atlassian either retain the existing attachment access functionality or provide an equivalent replacement before removing it. Customer data access should not be reduced as a side effect of user interface simplification.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.