Support Terms and Conditions
Access control
Section titled “Access control”- Required permission: canManageKnowledgeBase
- Fallback: Users without access see an access denied message.
Default behavior
Section titled “Default behavior”- Auto seed: If no custom terms exist for a shop, the app auto-persists and serves default terms content.
- Legacy upgrade: If old legacy default text is detected, it is automatically upgraded to the current default terms.
- Restore default: Admin can reset to default terms from UI action.
Admin page features
Section titled “Admin page features”- Large multiline editor for full terms text
- Save Terms action
- Restore Default Terms action
- Last updated timestamp indicator
- Shortcut link to open public customer terms page
Public page features
Section titled “Public page features”- Displays current terms as plain text with preserved line breaks
- Provides back link to Support Center
- No editing available on public page
How terms are enforced
Section titled “How terms are enforced”- Enforcement point: Customer ticket creation form in storefront Support Center
- Rule: Customer must check ‘I agree to the Support Terms and Conditions’
Data model
Section titled “Data model”- Table: SupportTerms
- Key: shop unique
Fields
Section titled “Fields”- content- createdAt- updatedAtOwner guidance
Section titled “Owner guidance”- Review terms with legal counsel before publishing.
- Keep wording aligned with Privacy Policy, Return Policy, and Shipping Policy.
- If you change dispute handling or retention policy, update terms immediately.
- Test customer ticket creation after edits to confirm checkbox flow still works.