A governance board requires that all OmniStudio components be documented to ensure future maintainability.

The most effective place for technical documentation is inside the Integration Procedure itself, using the Description and Internal Notes fields on the procedure and its elements. This keeps the explanation directly beside the configuration it describes, which improves maintainability for future consultants, admins, and developers. Storing the documentation only in the component name is too limited and quickly becomes unreadable. Saying OmniStudio components are self-documenting is false; declarative components still need design intent, assumptions, dependencies, and troubleshooting notes. A Word document on a rarely updated shared drive creates documentation drift. Salesforce identifies Internal Notes as designer-visible descriptive text, making it the proper location for technical implementation notes.

================