What option is not a step to create document types for applications?

The choice of removing access to the document from internal users is not a step involved in the process of creating document types for applications. The primary objective of establishing document types is to facilitate the organization, retrieval, and management of documents associated with specific applications, ensuring that users who need access can obtain it efficiently.

Turning on the Document Checklist is an essential step because it aids in defining the required documentation necessary for specific processes, enhancing the workflow involved in applications. Enabling Intelligent Document Automation is also critical, as it allows for the optimization and efficiency of document processing, which aligns well with the aims of managing document types. Creating a Document Type itself is a fundamental step in the process, establishing the framework for how documents are categorized and handled within the application system.

In contrast, restricting access by removing it from internal users would contradict the purpose of implementing effective document management strategies. It would lead to potential inefficiencies and challenges in collaboration and information sharing, which are vital in public sector solutions. Therefore, this choice stands out as it does not align with the necessary steps for creating document types.