# Ability to rename Extensions on Entity view

**URL:** <https://community.fibery.io/t/ability-to-rename-extensions-on-entity-view/967>\
**Category:** Ideas & Features\
**Created:** [September 9, 2020, 5:44pm UTC](https://community.fibery.io/t/ability-to-rename-extensions-on-entity-view/967 "2020-09-09T17:44:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 9, 2020, 5:44pm UTC](https://community.fibery.io/t/ability-to-rename-extensions-on-entity-view/967/1 "2020-09-09T17:44:49Z")

</div>

I would find it useful to be able to rename Extensions such as Comments or File Uploads to more clearly indicate what they’re to be used for. With comments, for example, on a Contact it might make more sense to rename this to “interactions” and to use it to record every time you interacted with a contact (e.g. call, email, etc.). With other things it might be useful to rename it “Updates”. The differences may seem minor, but I think it would enhance clarity. Especially if you imagine interacting with the system as a non-admin user, someone who has no idea about how the back-end works, or what “extensions” are.

Basically I want to use Comment as a universal stand-in for sequential, dated updates to a variety of Types and each one may have different terminology or concept for what an “update” really is.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [September 15, 2020, 10:04pm UTC](https://community.fibery.io/t/ability-to-rename-extensions-on-entity-view/967/2 "2020-09-15T22:04:17Z")

</div>

To add to and clarify this, with Files for instance, it could also be good to be able to indicate what the purpose of those files are by naming the field. On a construction project Entity, we might want to have only architectural plans, for example.

Of course one day to have folders or other organization for file uploads would be nice. Or at least the ability to add and customize multiple File extension instances.

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [October 23, 2025, 1:36pm UTC](https://community.fibery.io/t/ability-to-rename-extensions-on-entity-view/967/3 "2025-10-23T13:36:11Z")

</div>

Fixed for Files

> [@October 23, 2025 / sauropod Multiple Files Fields per Database and some unexpected improvements](https://community.fibery.io/t/october-23-2025-multiple-files-fields-per-database-and-some-unexpected-improvements/9871):
>
> Multiple Files Fields per Database Now (and finally!) you can add multiple File Fields to any database and define whether each field allows one or many files. Previously, only a single File Field was supported, which created several annoying limitations. This update removes that restriction and our hands are free to improve files support in Fibery further person_getting_massage. Some new small things related to files in this release: Refined the File Field UI (a little bit) Added …