Configure E-Signature Provider and Signing Method Per Organization
The global administration portal includes configuration settings for the document signing infrastructure. The Global Administrator can assign an e-signature provider per organization, configure API credentials and webhook endpoints for Signicat or alternative providers, and define document type policies (e.g., 'power of attorney' always requires BankID signing; 'consent form' may use in-app acknowledgment). These settings are stored as organization-level configuration and applied at runtime by the document signing service when initiating new signing sessions. Changes take effect for new signing requests without affecting in-progress sessions.
User Story
Acceptance Criteria
- Given the global administrator accesses the document signing configuration for an organization, when they select an e-signature provider from the supported list, then the configuration is saved and applied to all new signing sessions for that organization
- Given a provider is configured, when the administrator enters API credentials and webhook URLs, then the system validates the connection to the external provider before saving
- Given document type signing policies are configured, when an organization administrator initiates a signing workflow for a specific document type, then only the signing methods permitted by policy are offered as options
- Given the global admin updates a provider configuration, when existing in-progress signing sessions are checked, then they continue using the previous provider configuration without interruption
- Given an organization has no e-signature provider configured, when an organization administrator attempts to initiate a BankID signing workflow, then an informative error is shown directing them to contact the global administrator
Business Value
Different organizations have different legal obligations and vendor relationships. Configuring e-signature providers at the platform level ensures the Global Administrator can onboard new organizations with their specific signing requirements without code changes, and gives each organization the correct legal signing tool. Centralizing this configuration also makes provider migrations straightforward — if Signicat is replaced, only one configuration change is needed rather than per-organization updates.
Components
- Document Signing Infrastructure infrastructure
- Document Signing Service service
- POA Service service