Advanced Operations

What this page is for

Advanced Operations stores low-frequency controls for freeze reasons, webhook policy, staff availability policy, and push/system notification templates.

Who should use it

Owner, operations manager, platform admin

Where to find it

/admin/advanced

Before you start

• Advanced operations fields are Freeze reason codes, Webhook policy JSON, Staff availability policy JSON, Template name, Push title, and Push body.
• Freeze reason codes are one reason per line and are used by branch auto-approval and membership freeze workflows.
• Webhook policy JSON controls provider callback handling policy. It should be valid JSON and changed only by someone who understands payment and messaging webhooks.
• Staff availability policy JSON is the default policy layer. Individual staff availability remains in the staff Preferences drawer.
• Template name identifies the push/system notification template internally. Push title and Push body are the message shown to staff or customers.
• Push/system templates should be created only for real events and tested through the related workflow before launch.

Daily workflow

• Update freeze reasons when owner policy changes, then test one freeze request path that uses the reason list.
• Review webhook account health after changing policy and confirm payment or message callbacks still process.
• Create push template, trigger a safe internal test event, and confirm wording before customer-facing use.

Watch out

• Do not paste secrets into JSON policy fields or push template content. Credentials belong in provider credential setup only.

Related help

• Use the left menu to open related pages in Admin Settings.
• Use Ask Docs for questions that are already covered in this public documentation.