01Purpose of release notes
Finger Manager continuously improves product capabilities. Release notes help enterprise customers understand shipped changes and use them for internal training, launch review, and system review.
- New features
- Module changes
- Workflow improvements
- Bug fixes
- Security enhancements
- API and integration changes
- Changes that may affect existing usage
02Update types
Release notes classify changes into new features, improvements, fixes, security updates, and API or integration updates.
- New features: new product, module, or configuration capabilities such as client tags, KYC supplement reminders, mobile task handling, risk categories, report queues, and team permission configuration
- Improvements: optimization of existing experience, performance, or manageability such as client filtering, task status display, mobile notification speed, report generation, review page layout, and permission configuration
- Fixes: corrections for known issues such as inconsistent task status, delayed mobile notifications, failed report export, unsaved filters, or role access issues
- Security updates: account security, permission checks, audit records, abnormal access alerts, API credential management, and sensitive operation confirmation
- API and integration updates: new API fields, Webhook events, response structures, permission scopes, error code descriptions, and request signature enhancements
03Release note format
Each release note should include version number, release date, summary, detailed changes, impact scope, and recommended actions when configuration, training, or integration updates are needed.
- Version number such as v1.0.0, v1.1.0, or v1.2.3
- Release date
- Update summary
- Changes grouped by category
- Affected teams, modules, or usage scenarios
- Recommended administrator or team actions
04Example release note
v1.0.0, released on June 9, 2026. Finger Manager documentation center and foundational resource pages launched.
- Added Terms of Service page
- Added Privacy Policy page
- Added Refund Policy page
- Added Documentation center
- Added Product Concepts documentation
- Added Workflow Structure documentation
- Added Role Model documentation
- Added Implementation Planning documentation
- Added Operating Reference documentation
- Impact: website resource menu, App Store review materials, enterprise customer evaluation materials
- Recommended actions: add Terms of Service, Privacy Policy, and Refund Policy entries to the website menu; enter the privacy policy URL in App Store Connect; reference the Refund Policy page in Paddle and Stripe review materials
05Administrator update notes
Enterprise administrators should pay attention to changes that affect permissions, member management, modules, report exports, workflows, security settings, and API credentials. If an update affects existing workflows, administrators should notify internal teams.
- Permission model changes
- Member management changes
- Module enablement changes
- Report export permission changes
- Workflow status changes
- Security setting changes
- API credential changes
06Operations team update notes
Operations teams should watch for changes to client management pages, task queues, review flows, mobile reminders, report generation, notes, and attachments. Internal SOPs and training materials should be updated when operation methods change.
- Client management page changes
- Task queue changes
- Review flow changes
- Mobile reminder changes
- Report generation changes
- Notes and attachment changes
07Risk and compliance update notes
Risk and compliance teams should review changes related to risk alert rules, KYC status display, permission records, audit logs, exception workflows, exports, and records retention.
- Risk alert rule changes
- KYC status display changes
- Permission record changes
- Audit log changes
- Exception workflow changes
- Data export and record-retention changes
08IT and implementation update notes
IT and implementation teams should review API fields, Webhook events, interface permissions, error codes, security signatures, and integration method changes. Compatibility-impacting updates should be verified in test environments before production.
- API field changes
- Webhook event changes
- Interface permission changes
- Error code changes
- Security signature changes
- System integration changes
09Update notification methods
Finger Manager may publish or notify updates through different channels depending on importance and customer configuration.
- Website release notes page
- In-app notifications
- Administrator notices
- Email notices
- Version notes
- Customer support communication
- Documentation center updates
10Version compatibility notes
Finger Manager tries to maintain reasonable compatibility for important feature changes, but enterprises may need configuration or integration adjustments after major changes.
- API version upgrades
- Permission model changes
- Module structure changes
- Data field changes
- Security strategy upgrades
- Third-party service changes
11History
Release Notes will continue to record important Finger Manager changes and can be used as a reference for internal review, training, implementation, and retrospectives.
- Product evolution
- Internal review
- Training reference
- Implementation reference
- Retrospective reference
