# Attachments and AuthAccount capabilities preview release

**URL:** <https://forum.flow.com/t/attachments-and-authaccount-capabilities-preview-release/4239>\
**Category:** 🏄🏻‍♀️ Cadence\
**Created:** [February 1, 2023, 6:21pm UTC](https://forum.flow.com/t/attachments-and-authaccount-capabilities-preview-release/4239 "2023-02-01T18:21:30Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![sainati](https://avatars.discourse-cdn.com/v4/letter/s/f1d935/32.png) [@sainati](https://forum.flow.com/u/sainati)\
**Post date:** [February 13, 2023, 6:35pm UTC](https://forum.flow.com/t/attachments-and-authaccount-capabilities-preview-release/4239/6 "2023-02-13T18:35:24Z")

</div>

> [@C-3PFLO](#):
>
> What access is required to attach or remove an attachment from a resource?

Only the owner of a resource (i.e. the person who has the actual resource value as opposed to a reference to it) is able to add or remove attachments from it. Anybody who possesses a reference (with the proper type) can access the attachments on a resource however.

> Also, is there a way to restrict removal even from the owner of the resource.

This was a feature that was discussed but was not included in the initial release of the attachments feature. If there’s a compelling use case for restricting removal we can consider adding it though.

---

_[View the full topic](https://forum.flow.com/t/attachments-and-authaccount-capabilities-preview-release/4239)._
