API Docs / Schemas / EngagementSettingsDto

EngagementSettingsDto

Tenant-level configuration for engagement behavior, branding, and notification settings.
Controls how engagements are presented to clients, what happens when they're accepted,
and how engagement emails are formatted and delivered.

Properties

Name Type Description
codestring

Unique identifier for the settings

Unique identifier for the settings

introContentBlockCodeAndNameDto
thankYouContentBlockCodeAndNameDto
emailContentBlockCodeAndNameDto
acceptanceTaskCodeAndNameDto
notifyClientManagerOnAcceptanceboolean

Whether to send an email notification to the client manager when an engagement is accepted

Whether to send an email notification to the client manager when an engagement is accepted

notifyPartnerOnAcceptanceboolean

Whether to send an email notification to the partner when an engagement is accepted

Whether to send an email notification to the partner when an engagement is accepted

designThemeCodeAndNameDto
showPracticeNameboolean

Whether to display the practice name on engagement acceptance pages and documents

Whether to display the practice name on engagement acceptance pages and documents

attachPDFsboolean

Whether to attach engagement PDFs to the engagement email

Whether to attach engagement PDFs to the engagement email

thankYouEmailContentBlockCodeAndNameDto
requestDdMandateboolean

Whether to request a Direct Debit mandate when engagement is accepted

Whether to request a Direct Debit mandate when engagement is accepted

requestAmlOnboardingboolean

Whether to request AML onboarding for the main contact when engagement is accepted

Whether to request AML onboarding for the main contact when engagement is accepted

amlOnboardingLevelIdstring

The AML platform onboarding level ID to use when creating the onboarding request

The AML platform onboarding level ID to use when creating the onboarding request

signaturePageContentBlockCodeAndNameDto
useThirdPartyProposalPlatformboolean

Whether to use a third-party platform (e.g., Socket) for proposals instead of native Sodium proposals

Whether to use a third-party platform (e.g., Socket) for proposals instead of native Sodium proposals

addToPipelineOnSendboolean

Whether to add the client to a sales pipeline when their proposal is first sent

Whether to add the client to a sales pipeline when their proposal is first sent

onSendPipelineCodeAndNameDto

JSON Example

{
  "code": "string",
  "introContentBlock": {
    "code": "string",
    "name": "string"
  },
  "thankYouContentBlock": {
    "code": "string",
    "name": "string"
  },
  "emailContentBlock": {
    "code": "string",
    "name": "string"
  },
  "acceptanceTask": {
    "code": "string",
    "name": "string"
  }
}

Used By Operations