# Advanced Document Management

### Advanced Document Management Overview <a href="#hz7fdeaa8vso" id="hz7fdeaa8vso"></a>

Advanced *Document Management* equips *NetSuite* administrators with a modern, centralized approach to managing files and attachments across their organization. Through a structured *SuiteApp* installation, the system replaces outdated file handling practices with a flexible, role-based document framework that improves visibility, organization, and compliance.

Initial setup involves installing the *SuiteApp* and verifying readiness via the *Advanced Attachments* menu. From there, users can configure the solution using either the *Standard* or *Legacy* settings, though most new customers are directed toward the Standard model for long-term support and feature compatibility.

Once enabled, *Advanced Attachment Settings* allow files to be managed across all or selected record types, offering the ability to name custom tabs, restrict access by role, and unify file display through a consistent interface. Storage options are equally adaptable, organizations can continue using the default *NetSuite File Cabinet* or opt into *AWS S3* integration for higher capacity needs.

For customers with legacy agreements, **Charted** *File Storage* remains supported but is no longer available to new users. Administrators can also define behavior at the record level using the *AAB Record Type Settings* table, adjusting everything from tab names and drag-and-drop zone sizes to storage locations and audience access. Together, these tools create a scalable and secure environment for managing business-critical documents in *NetSuite*.

### Navigate the Documentation

Use the links below to access individual guides for each part of the Advanced Document Management setup process:

#### Getting Started

* [Introduction and Initial Installation<br>](/ap-automation/charted-configuration/advanced-document-management/introduction-and-initial-installation.md)Overview of the Advanced Document Management feature set and instructions for installing the required bundle.<br>
* [Legacy and Standard Settings<br>](/ap-automation/charted-configuration/advanced-document-management/legacy-and-standard-settings.md)Configure standard and legacy attachment handling behavior to control how files are managed and displayed.

#### Configuration & Customization

* [Configuring Advanced Attachment Settings<br>](/ap-automation/charted-configuration/advanced-document-management/configuring-advanced-attachment-settings.md)Enable advanced file-attachment logic, including naming conventions, overwrite behavior, and audit tracking.<br>
* [Working with NetSuite File Cabinet and AWS S3 Storage<br>](/ap-automation/charted-configuration/advanced-document-management/working-with-netsuite-file-cabinet-and-aws-s3-storage.md)Set up dual storage options using the native File Cabinet and Amazon S3 for secure, scalable document handling.<br>
* [Customizing Record Types and Additional Options<br>](/ap-automation/charted-configuration/advanced-document-management/customizing-record-types-and-additional-options.md)Apply document management settings by record type, define custom rules, and activate additional upload options.

\
Below you will find a detailed description of the content of the articles.

#### [Introduction and Initial Installation](/ap-automation/charted-configuration/advanced-document-management/introduction-and-initial-installation.md)

*Advanced Document Management* begins with the installation of a dedicated *SuiteApp* that modernizes how files are stored, organized, and retrieved within *NetSuite*. This installation process ensures that administrators have access to a centralized framework for managing attachments more efficiently. The steps involve navigating to the *SuiteBundler* interface, searching for the specific bundle ID, reviewing the bundle details, and completing the installation through *NetSuite’s* guided interface. Once installed, users can confirm activation by locating the new “Advanced Attachments” option under the *Setup* menu. These actions prepare the environment for further configuration and mark the first step in replacing manual document processes with automated, role-based file control.

#### [Legacy and Standard Settings](/ap-automation/charted-configuration/advanced-document-management/legacy-and-standard-settings.md)

*Advanced Document Management* provides two configuration paths for managing file attachments in *NetSuite*: the Standard settings and the Legacy settings. Administrators access both options through the *Advanced Attachments* menu, where they can determine which method is active in their environment. The *Standard* settings are recommended for all new customers, offering current support and compatibility with future updates. In contrast, *Legacy* settings remain available only for a limited group of long-time users and are no longer assigned to new implementations.

#### [Configuring Advanced Attachment Settings](/ap-automation/charted-configuration/advanced-document-management/configuring-advanced-attachment-settings.md)

Configuring *Advanced Attachment Settings* is a critical step in activating document control features across *NetSuite* records. Administrators start by enabling the functionality from the Advanced Attachments settings page, which allows files to be attached in a structured way using a dedicated tab on each record. They can choose to apply this configuration globally to all supported record types or selectively enable it per record. Customization options include renaming the file tab and assigning specific user roles that can view or manage attachments. This setup not only enhances visibility and consistency but also strengthens security by limiting access based on role.

#### [Working with NetSuite File Cabinet and AWS S3 Storage](/ap-automation/charted-configuration/advanced-document-management/working-with-netsuite-file-cabinet-and-aws-s3-storage.md)

*Advanced Document Management* supports multiple storage options, giving administrators flexibility based on their organization’s needs. Most environments rely on the *NetSuite* *File Cabinet*, which is the default and typically does not require any changes. However, the system also supports *AWS S3* for customers who deal with large volumes of data and need additional storage capacity. *AWS* integration is optional and usually only relevant for high-storage use cases where administrators manage the setup independently.

Lastly, **Charted** *File Storage* is still visible in the settings but is inactive for anyone who isn’t a legacy customer. This option has been phased out and remains only for existing accounts that were already using it.

#### [Customizing Record Types and Additional Options](/ap-automation/charted-configuration/advanced-document-management/customizing-record-types-and-additional-options.md)

The customization of record-level settings in *Advanced Document Management* allows administrators to control exactly how attachments are handled for each record type in NetSuite. Using the *AAB Record Type Settings* table, they can enable or disable the feature per record, rename the attachments tab, adjust how PDFs display, and resize the drag-and-drop upload area. Role-based access can also be defined to limit visibility to specific user groups.

Storage behavior can be tailored as well, with options to assign file paths within the *NetSuite File Cabinet* or, for high-volume needs, configure *AWS S3* folders for certain records. Administrators can even disable the native *NetSuite Files* tab to streamline visibility and tighten access controls. These tools offer precise, flexible control over how documents are stored, viewed, and secured on a per-record basis.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.charted.com/ap-automation/charted-configuration/advanced-document-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.