> ## Documentation Index
> Fetch the complete documentation index at: https://forest-chore-open-api.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Import, rename & remove fields

When building your back-office, you will probably want to hide as much complexity from your users as you can.

This includes:

* Hiding technical and confidential fields
* Using naming conventions that the final user understands

## Moving fields

Import fields from single record relationships into your collections.

The imported fields will behave as if they were on that collection.

```javascript theme={null}
// Assuming the following structure:
// User    { id, firstName, lastName, addressId }
// Address { id, streetName, streetNumber, city, countryId }
// Country { id, name }

userCollection
  .importField('city', { path: 'address:city', readonly: true })
  .importField('country', { path: 'address:country:name', readonly: true });
```

<Info>
  When using `readonly: false`, the referenced record fields can be edited.
</Info>

## Renaming and removing fields and relations

Rename and remove fields or relations by calling the `renameField` and `removeField` methods.

```javascript theme={null}
collection.renameField('account_v3_uuid_new', 'account').removeField('password');
```

<Warning>
  Renamed and removed fields are renamed and removed **only in the back-office**.

  In your code:

  * Removed fields are still accessible (for instance, as dependencies to compute new fields)
  * Renamed fields must still be referred to by using their original name
</Warning>