# Setting Up Model & Artifact Objects (eTMF & Study Startup)
Whether your organization uses the _Model_ and _Artifact_ objects to reflect the TMF Reference Model, to support auto-filing for Study Startup binders, or both, this article will help you understand how to configure and work with these objects.
Note: This feature is only available on Clinical Operations eTMF and Clinical Operations Study Startup Vaults.
## About the Filing Model
Users can define _Filing Model_ on both binder templates and individual binders. This field instructs Vault to use specific auto-filing behaviors.
* **Binder Section to Document Type**: This supports the pre-V13 auto-filing behavior, wherein the name of the document type must match the name of the binder section.
* **TMF RM 2.0, TMF RM 3.0. etc.**: This uses a match of the artifact mapped to a document type to the artifact (zone/section) mapped to a binder section to drive auto-filing.
* **Vault Clinical Docs**: This uses a match of the artifact mapped to a document type to the artifact mapped to a binder section to drive auto-filing. The auto-filing logic is different from that used with TMF RMs.
Note that although you can add this field to other document types, auto-filing will only work on binders with certain document types:
* For _TMF RM_ or _Binder Section to Document Type_ filing models: _Trial Master File_, _Country Master File_, and _Site Master File_ (eTMF Vaults created before V10) or _Study Level File_, _Study Country Level File_, and _Study Site Level File_ (newer Vaults)
* For _Vault Clinical Docs_ filing model: _Study Start-Up Packages_ or any custom subtypes/classifications under this document type
## About Model & Artifact Document Fields
There are several shared document fields associated with _Model_ and _Artifact_ objects:
* **Model**: By default, this shared field is not associated to any document types. When you add it to document types, it will simply show users what models are associated (via the document type configuration) with each document. On documents, this field value will not be editable.
* **Artifact**: By default, this shared field is not associated to any document types. When you add it to document types, it will show users what artifacts are associated (via the document type configuration) with each document. On documents, this field value will not be editable.
## How to Add the Artifact Field to Document Types
For auto-filing to work correctly, you must associate the standard, shared _Artifacts_ field with any document types, subtypes, or classifications that should auto-file into binders. Learn how in [Working with Shared Fields](/en/lr/4884/#use-shared-field).
## How to Associate Document Classifications to Artifacts
When you associate artifacts to a document classification, you define field values for documents with that classification. This behavior does not work like other field defaulting. Firstly, Vault updates the fields on existing documents whenever the document type setting updates, rather than only during initial document creation. Secondly, these fields are read-only for all users, meaning that the values Vault auto-populates are read-only. Vault uses these document fields to facilitate binder auto-filing.
To assign an artifact to a document classification:
1. Navigate to **Admin > Configuration > Document Types** and open the details dialog for a specific classification.
2. In the **Type Defaults** tab, under Reference Models, select an artifact for each reference model.
3. Click **Save**.
Although these settings are available at any level in the document type hierarchy (_Base_, _Type_, _Subtype_, or _Classification_), only the _Classification_ level is relevant for most eTMF customers.
## How to Associate Document Classifications to Subartifacts {#subartifacts}
_Subartifacts_ further refine the _Classification_ of a document through the _Subartifact_ document field, which negates the requirement for a separate Classification for TMF Reference Model subartifacts.
### Enabling Subartifact Document Fields
To enable _Subartifact_ document fields:
1. Navigate to **Settings > Application Settings > eTMF Features > Enable Subartifacts**.
2. Click **Edit**.
3. Select the **Enable Subartifacts** checkbox.
4. Click **Save**.
### Assigning Subartifact Objects to Document Classifications
To assign a _Subartifact_ object to a document classification:
1. Navigate to **Business Admin > Objects > Subartifacts**.
2. Click **Create**.
3. In the _Details_ section, name the **Subartifact** and set the status to _Active_.
4. Assign a Document Classification for the **Subartifact**.
5. Click **Save**.
### Assigning Subartifact Objects to EDL Item Templates
EDL Items include a _Subartifact_ field where the subartifact is defined. When this value is populated, Vault matches the EDL item to the document that matches on both the Classification and Subartifact, along with other matching criteria that may be applied.
1. Navigate to the _EDL Item Template_ object, either through a custom tab or in **Business Admin > Objects > Template EDLs**.
2. Click **Create**.
3. Fill the required fields and add **Subartifact** to the _Matching EDL Item Fields_.
4. In the _EDL Item Template Detail Page Layout_, add the **Subartifact** field.
5. Click **Save**.
Note: To enable Subartifacts for Expected Document Lists, Admins must add Subartifacts as a matching field.
## How to Associate Binder Template Sections to Artifacts
By associating binder sections to a specific artifact (zone or section), you enable Vault to auto-file documents into a binder that properly uses the TMF RM structure.
To assign an artifact to a section in a binder template:
1. Navigate to **Admin > Business Admin > Templates: Binders & Documents**.
2. In the **Template Location** panel, select a document type.
3. Open a specific binder template.
4. Under Details, click **Edit**.
5. Select a **Filing Model**.
6. Click **Save**.
7. Under Binder Structure, click **Edit**.
8. For each binder section, select **Edit** from the **Actions** menu. If you're using one of the TMF RM options for _Filing Model_, select a specific artifact in the **Hierarchy Mapping** field. This list automatically filters to show only artifacts associated to the filing model.
9. Click **Save** when finished.
When you associate binder sections in a template to specific artifacts, Vault can only apply these mappings to binders created after saving the template changes. Any binders that were already created using the template are not affected. See [below][2] for details on editing section mappings for existing binders.
## How to Associate Binder Sections to Artifacts {#binder_section}
By associating binder sections to a specific artifact (zone or section), you enable Vault to auto-file documents into a binder that properly uses the TMF RM structure. If a binder was created from a template with the correct filing model and artifact mappings, you do not need to edit sections within individual binders. However, Vault allows you to select a different filing model and artifact mappings on individual binders for situations where a binder was created from a template that is not correct.
To assign an artifact to a section in an individual binder:
1. Open the binder.
2. In the document fields panel, click **Edit**.
3. Select a **Filing Model**.
4. Click **Save**.
5. Click **Edit Binder** and open the **Outline View** for the binder.
6. For each binder section, select **Details** from the **Actions** menu. If you're using one of the TMF RM options for _Filing Model_, select a specific artifact in the **Hierarchy Mapping** field. This list automatically filters to show only artifacts associated to the filing model.
7. Click **Done Editing** when finished.
[2]: #binder_section
[3]: #subartifacts