Which types of integration usually do not use their own ISU?

Document Transformation is the type of integration that typically does not use its own Integration System User (ISU). This is primarily because Document Transformation focuses on converting data from one format to another, allowing for easier data exchange between systems without requiring a dedicated ISU for the process.

In contrast, the other integration types often need their own ISU for authentication and authorization purposes to ensure secure data transmission and proper access control between systems. API Integrations, for instance, rely on ISUs to handle requests and secure communications effectively. Data Stream Integrations also require ISUs as they continuously manage and process data flowing between systems. Departmental Integrations, being more specific to departmental needs, usually have defined roles and permissions that necessitate their own ISU to maintain security and accountability in data handling.

Thus, Document Transformation stands out in this context as it serves a specific function that is less reliant on an ISU, thereby streamlining the data conversion process without the overhead of additional user management.