Our organization supports over 200 individual buildings, each with hundreds of recurring document templates such as procedures, compliance forms, access authorizations, and operational approvals. Today, all templates exist in a single list, which creates the following challenges:

Difficult template discovery and slower user workflows
Increased risk of selecting the wrong template for the wrong building
Limited ability to delegate ownership or manage access by location or team
Poor scalability as the number of templates continues to grow

Introduce template folders and subfolders within Acrobat Sign that allow administrators to organize templates by logical groupings such as:

Building or site identifier
Region or geography
Department or function
Document type or workflow

Folders should support role based permissions so that users only see and use templates relevant to their assigned buildings or responsibilities.
Key Functional Requirements

Create, rename, and delete template folders
Nested folders to support multi level organization
Ability to move existing templates into folders without breaking workflows
Folder level permissions for view, edit, and send
Search and filtering that respects folder structure
Optional folder level metadata such as building ID or cost center

Operational Impact

This capability would significantly improve governance, accuracy, and speed for large enterprises. It would reduce user error, simplify onboarding, and make Acrobat Sign far more viable for customers managing hundreds or thousands of templates tied to physical assets.

Strategic Value to Adobe

Supporting template folders positions Acrobat Sign as an enterprise ready platform for regulated and infrastructure heavy industries. It strengthens competitive differentiation and reduces friction for customers scaling digital signature workflows across complex operational footprints.