> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/release-notes/2026-release-notes/september-2026-release-notes.md).
# September 2026 Release Notes
## Core Application Updates
### Depreciation Updates
#### Fiscal Year Depreciation Support
We have introduced comprehensive support for fiscal accounting calendars, a critical requirement for government, education, and enterprise finance teams.
* **Organization-Level Fiscal Start**: A new **Fiscal month start** setting under **Organization Preferences** allows administrators to define the first month of their organization's fiscal year.
* **Collection-Level Calculation Start**: Administrators can now choose between **Calendar** or **Fiscal** periods for each depreciation-enabled collection.
* **Fiscal Period Boundaries**: When Fiscal is enabled, the system automatically derives all period boundaries (Months, Quarters, and Years) from the organization's fiscal start month.
* *Example*: If the fiscal year starts in April, Q1 is defined as April–June, and the fiscal year runs through the following March.
* **Fiscal Labeling**: All depreciation schedules, reports, and exports are enriched with derived fiscal labels (e.g., "Q1 FY2027"). The labeling convention is based on the calendar year in which the fiscal year begins.
* **Calculation Integrity**: Switching between Calendar and Fiscal boundaries changes period alignment and grouping only; it does not introduce different depreciation formulas or modify underlying record-level inputs like Asset Cost or Useful Life.
* **Consistent Reporting**: The same fiscal interpretation is used consistently across the Depreciation Summary, Table View, Chart View, and all generated reports, ensuring a unified view of financial data.
#### Customizable Depreciation Calculation Frequency
Administrators now have granular control over how and when asset depreciation is calculated and presented, allowing for better alignment with internal financial cycles.
* **Quarterly & Yearly Options**: In addition to the default Monthly frequency, administrators can now configure collections to use **Quarterly** or **Yearly** calculation frequencies via the **Manage depreciation** modal.
* **Aggregated Calculations**: Quarterly and Yearly amounts are produced by aggregating the underlying monthly calculations. This ensures that each depreciation type's documented principles, depreciable amounts, and salvage floors remain byte-for-byte identical to the monthly path.
* **Unified Schedule Display**: When a new frequency is selected, the entire depreciation schedule—including Table View, Chart View, and the Record Summary—updates to reflect the new period granularity (e.g., "Q1 2026 (Jan - Mar)" or "2026").
* **Recalculation Confirmation**: Changing a collection's frequency triggers a mandatory recalculation of all records. A confirmation modal warns administrators that existing calculated data will be replaced by the new frequency-based schedule.
* **Standardized Useful Life**: Regardless of the selected frequency, **Useful Life** remains expressed and validated in months, preventing confusion and ensuring data consistency during frequency changes.
* **Current Period Tracking**: The "Current Period" indicator and summary tiles automatically adapt to the active frequency, showing the applicable quarter or year and its corresponding month range.
#### Proration for Stub Periods in Quarterly and Yearly Depreciation
To ensure precise financial compliance, we have introduced support for proration during partial or "stub" periods within Quarterly and Yearly depreciation schedules.
* **Stub Period Definition**: A stub period is any Quarterly or Yearly depreciation period that contains fewer months than a normal full period (e.g., a 1-month or 2-month quarter).
* **Proportional Calculation**: Depreciation for stub periods is now calculated proportionally based on the number of complete applicable months within the period.
* **Quarterly Stubs**: Prorated as 1/3 or 2/3 of the full-quarter amount.
* **Yearly Stubs**: Prorated as `applicable months / 12` of the full-year amount.
* **Lifecycle Alignment**: Stub periods are automatically created when the **Date Placed in Service**, **Useful Life**, or **Stop Depreciation** date does not align exactly with a period boundary.
* **Useful Life Integrity**: The system now strictly respects the configured month-based Useful Life. For example, a 14-month useful life on a quarterly collection will generate four full quarters and one 2-month stub, ensuring the asset does not depreciate for longer than intended.
* **Calculation Granularity**: All proration logic continues to operate at a minimum granularity of one month, maintaining consistency with existing first-of-month normalization behavior.
* **UI Transparency**: A new information tooltip has been added to the **Useful life (months)** field on record forms, clarifying that proration will be applied for stub periods when Quarterly or Yearly frequencies are active.
#### Mid-Cycle Adjustments and Stop Depreciation
We are significantly enhancing our depreciation engine to provide the flexibility required for complex financial reporting and asset lifecycle management across all calculation frequencies.
* **Mid-Cycle Adjustments**: Administrators can now make adjustments to quarterly and yearly depreciation schedules even after they have commenced. This ensures valuations remain accurate despite changes in asset usage, cost, or salvage value.
* **Frequency-Dependent Start Periods**: The "Adjust depreciation" workflow now dynamically adapts to the collection's frequency. Users select a specific **Month**, **Quarter**, or **Year** as the start period for the adjustment.
* **Stop Depreciation Support**: We have extended the "Stop depreciation" functionality to Quarterly and Yearly frequencies. Administrators can halt depreciation schedules early, providing better control over retired or fully depreciated assets.
* **Chronological Event Processing**: The system now supports multiple mid-cycle adjustments followed by a stop event, processing each chronologically. Each event uses the depreciation state resulting from the previous adjustment to ensure calculation integrity.
* **Validation & Safeguards**: New validations prevent adjustments from starting before depreciation begins, after it completes, or after an effective stop date. The system also ensures that disabling mid-cycle adjustments for a collection does not remove existing adjustment history or recalculate current schedules.
* **Cross-Platform Consistency**: These advanced management tools are fully supported across Web, iOS, and Android, with all UI components (Table View, Chart View, and Summary) reflecting the adjusted schedules.
### Per-User Default Field Values
We are introducing a highly requested personalization feature that allows individual users to define their own default values for frequently used fields, significantly reducing repetitive data entry and improving workflow efficiency.
* **Personalized Data Entry**: Users can now configure their own default values for **Pull From** fields via a new **"My field defaults"** management interface located in the collection header
* **Smart Precedence Logic**: The platform implements a sophisticated hierarchy for pre-filling fields during record creation:
1. **Form-Level Autofill**: Takes the highest priority if configured.
2. **Per-User Defaults**: Applied if no form-level autofill is present.
3. **Column/Type Defaults**: The standard administrator-configured defaults serve as the final fallback.
* **Granular Configuration**: The management UI allows users to set, update, or clear defaults for any **Pull From** field they have permission to access. For hierarchical Pull From fields, child defaults remain dependent on the selected parent value, ensuring data integrity.
* **Cross-Platform Synchronization**: Configured defaults are stored at the user level and are automatically synchronized across all supported platforms.
* **Full Mobile Support**: While configuration is performed on the Web, the **iOS and Android** applications fully honor these personalized defaults. When a mobile user creates a new record, their preferred values are automatically pre-populated, saving thousands of keystrokes in the field.
* **Security & Validation**: The system automatically ignores any default value that becomes invalid due to permission changes, record deletion, or updated filtering rules, falling back to the next level in the hierarchy.
### Manager Approval Workflow for Reservations
We are adding a critical security and operational gate to our Reservations module, allowing organizations to strictly control the allocation of high-value equipment and shared resources.
* **Optional Approval Gate**: Administrators can now enable a **"Require approval"** toggle at the collection level within the Reservation Settings. This allows for a tailored workflow where some collections require oversight while others remain self-service.
* **New Reservation Statuses**: To support this workflow, we have introduced two new system statuses:
* **Waiting for Approval**: The initial state for all new reservations when approval is required. Assets in this state are not yet considered "Reserved" and remain available for other requests until confirmed.
* **Declined**: A terminal state for requests that do not meet management criteria.
* **Approver Roles & Permissions**: A new **"Reservation approval"** permission has been added to the Custom Role engine. This allows administrators to delegate approval authority to specific managers or team leads without granting full administrative access.
* **Structured Decline Workflow**: When declining a request, approvers are required to provide a mandatory **Decline Reason**. This reason is stored with the reservation and communicated back to the requester to facilitate adjustments and resubmission.
* **Automated Lifecycle Management**:
* **Auto-Cancellation**: Reservations that are not approved by their scheduled Start Date and Time are automatically transitioned to a **Cancelled** state to prevent stale requests from cluttering the system.
* **Re-Approval Logic**: If an approved reservation is edited, it is automatically reset to **Waiting for Approval** to ensure that changes to dates or assets are re-verified by management.
* **Integrated Notifications**: The system triggers real-time alerts for key events, including new submission alerts for approvers and decline/expiration notifications for requesters, complete with direct "Review" actions.
* **Mobile Approval Capability**: Managers can review, approve, or decline reservation requests directly from the **iOS and Android** apps, ensuring that equipment workflows are never bottlenecked by a lack of desktop access.
### Support for PGK (Papua New Guinea Kina)
We have expanded our international currency support to include the **Papua New Guinea Kina (PGK)**, enabling organizations operating in the region to track asset costs and values in their local currency.
* **New Currency Option**: Administrators can now select **PGK - K (Papua New Guinea Kina)** for any Currency data type field across the platform.
* **Global Availability**: PGK is available for selection in **Organization Preferences**, as well as field settings for **Collections**, **Categories**, and **Admin Tools**.
* **Smart Search**: The currency selector is optimized for speed—you can find the new option by searching for "PGK", "K", "Kina", or "Papua".
* **Flexible Formatting**: The currency supports standard formatting options, including prefix (e.g., **K 1,234.56**) and suffix (e.g., **1,234.56 K**) positions, as well as customizable decimal and thousands separators.
* **Coexistence with MMK**: While both PGK and the Myanmar Kyat (MMK) share the symbol "K", the system distinguishes between them by their unique currency codes to ensure data integrity.
* **Seamless Data Handling**: PGK is fully supported across all core workflows, including **Imports** (recognizing the "K" symbol and "PGK" code), **Exports** (CSV, XLSX, and PDF), and **Relational Fields** (Pull From Collection).
* **Full Mobile Parity**: Field teams can view and enter PGK values directly from the **iOS and Android** apps, with all formatting settings automatically synchronized from the web.
* **Calculation Note**: As with all multi-currency environments in Asset Panda, performing math or summations across fields configured with different currencies will aggregate the raw values without performing a currency conversion.
### Android Offline Mode Optimization
We’re excited to announce that the latest version of our Android application, **Version 2.0.0**, is now live on the Google Play Store.\
This release brings major improvements to **Offline Mode**, focused on performance, visibility, and responsiveness when working with large asset datasets.
**Key Improvements:**
* **Faster Offline Downloads:** Reduced download time from approximately **7–8 hours to 1–2 hours**, depending on data volume and network conditions.
* **Enhanced Progress Tracking:** Real-time visibility into records fetched, records saved, total collections, and forms.
* **Collection-Level Status:** Clear indication of the collection currently being downloaded and successfully completed collections.
* **Optimised Search, Sort & Filter:** Results are displayed immediately while processing continues progressively in the background.
* **Improved User Experience:** Reduced waiting time, better responsiveness, and greater transparency when working with large offline datasets.
Overall, **Android 2.0.0 significantly improves Offline Mode performance and usability**, providing a faster and smoother experience for organisations managing large volumes of assets.
#### Mobile Offline Audits
Offline support for audits is now available on iOS and Android mobile devices, allowing field auditors to conduct full physical inventory audits in low-connectivity environments without interruption. The update eliminates the requirement for an active internet connection during physical scanning and verification.
* **Seamless Offline Execution**: Auditors can start and progress through active audits even when disconnected from cellular or Wi-Fi networks.
* **Immediate Local Caching**: Audit actions, including marking assets as audited, updating verification statuses, logging notes, and recording exceptions, are instantly saved locally to the device's secure data store.
* **Visual Sync Indicators**: While offline, scanned records display a **"Marked offline – will sync when online"** status banner to notify auditors that their actions have been safely recorded.
* **Automatic Background Synchronization**: The mobile app continuously monitors network availability. As soon as connectivity is restored, all queued audit actions automatically sync to the server in the background, updating the centralized audit log and live progress metrics.
* **Audit Integrity & Timestamp Precision**: To ensure strict compliance and audit trail accuracy, the system captures the exact physical timestamp and GPS location (where available) at the precise moment an asset is marked, preserving the chronological order of field actions regardless of when synchronization occurs.
* **Conflict & Error Resolution**: Once server synchronization is successfully confirmed, local queue records are cleared automatically. If any conflicts or network interruptions occur during sync, the app provides detailed error alerts and a manual retry option to ensure no data is lost.
### Delete Kit Templates
Administrators can now delete unused, obsolete, or outdated kit templates directly from Categories, enabling organizations to keep their kit catalog organized and streamlined.
* **Template Deletion from Categories**: Administrators can select and delete any kit template under the Categories collection.
* **Deletion Regardless of Usage**: Templates can be deleted regardless of whether they are actively assigned to existing kit records in collections.
* **Seamless Transition to Non-Template Kits**: Deleting a template is non-destructive to existing assets. Any active kits in collections that were built using the deleted template automatically convert to non-template (custom/standalone) kits, preserving all assigned items, components, and historical data intact.
* **Platform-Wide Synchronization**: Template deletions and kit status conversions reflect immediately across all surfaces, including the Web application and iOS and Android mobile apps.
* **Audit Trail & Activity Logging**: All kit template deletions are automatically logged in the centralized **Activity Stream** (Record Logs) as `"{Category name} category deleted in {Account} / {Module}"`, ensuring visibility for security and administrative audits.
### Email Files as an Attachment Field Type
**Attachment** fields now support email files, allowing organizations to upload, store, and manage correspondence, approvals, and communication records alongside their assets.
* **New "Email" Allowed File Type**: Administrators can enable **Email** as an allowed category in **Attachment** field configuration (`Field Settings → File types allowed`). The category specifically accepts `.eml` and `.msg` email formats.
* **Granular Field Configuration**: The Email file type joins the existing Image, Document, Video, and Audio options and can be checked or unchecked independently. By default, newly created **Attachment** fields have Email unchecked to maintain explicit administrative control.
* **Byte-for-Byte File Integrity**: Uploaded `.eml` and `.msg` files are preserved and downloaded byte-for-byte identical to the original file. No headers, routing metadata, or nested attachments are modified or stripped during upload or storage.
* **Dedicated Email File Icon & Metadata**: Email attachments render with a distinct email icon across Grid and Field Tile views, displaying full file metadata including original filename, file size, and upload timestamp.
* **Safe Handling & Previews**: When an email file is clicked, the system displays a secure "No preview available" modal with a direct **Download** action, ensuring raw email code and headers are not executed or rendered unsafely in browser web views.
* **Comprehensive Filtering**: The **File Type** filter across the centralized **Global Library** and the record-level **Attachments** tab now includes the **Email** category, allowing users to filter and locate email files.
* **Safe Deactivation Guardrails**: If an administrator unchecks **Email** on a field that already contains attached email files, existing attachments remain stored, searchable, and downloadable on records, while blocking new email uploads to the field.
* **Full Mobile Parity (iOS & Android)**: Field users can select and upload `.eml` and `.msg` files directly from their iOS and Android file pickers, filter attachments by Email, and download files on mobile devices with complete offline queueing support.
### Organize Attachments with Folders
Attachment folders are now supported across the global attachment gallery and record-level attachment galleries, enabling teams to manage large volumes of files in more organized folder hierarchies.
* **Global Attachment Gallery** (`Tools → Attachments`): Organize organization-wide files into global folders.
* **Record-Level Attachment Gallery** (`Record Details → Attachments tab`): Structure attachments belonging to an individual asset or record into dedicated, record-specific folders.
Global and record-level folder structures operate independently.
Users can create, rename, and delete folders, subject to standard naming validations and role-based user permissions. They can also select attachments to move files between folders and upload files within a folder while viewing it.
To prevent accidental data loss, deleting a folder requires users to resolve or move any contained attachments first. Deleting an empty folder removes only the folder container without impacting underlying records or global libraries.
Attachment folders are supported in the desktop application and from the iOS and Android companion apps.
See [Attachments](/tools/attachments.md).
### Redesigned Record Activity & Change Logs *(Early Access)*
The **Activity** tab for records and account-wide **Record Logs** view have been updated to improve the process of tracking updates. You can review field changes, filter by specific details, and download complete history reports.
* Field changes are presented in a table showing the **Date & Time**, **Who made the change**, **Action**, **Field Name**, **Previous Value**, and **New Value**.
* Addresses & GPS coordinates are displayed as direct, clickable map links so you can view locations instantly.
* Signatures and dates are formatted inside the table so records stay organized and legible.
* Unchanged fields are hidden so you only see what actually changed.
* The table indicates if the change was made by a user on the web or mobile app, submitted via a form, updated by an automated rule, or synced through an Import or integration
* Quickly search and filter your logs by specific fields, team members, actions (created, updated, deleted), or date ranges to understand when and why an update occurred.
You can also export your activity history from a record’s **Activity** tab or the Record Logs page to support audits and compliance reporting.
{% hint style="info" %}
This update is currently rolling out under a feature flag so raise a request to have this enabled for your account.
{% endhint %}
### Conditional Visibility for Additional Pulled Fields in Forms
Administrators can now configure Show/Hide rules for each additional Pull From field independently. Additional pulled fields are no longer treated as an all-or-nothing bundle with the primary Pull From field, allowing you to show or hide specific pulled details (such as serial numbers, specifications, or assigned locations) as needed.
They can select any additional Pull From field as the target prompt when creating:
* **Show Prompt Rules**: Keeps the additional pulled field hidden by default and reveals it only when the specified form condition is met.
* **Hide Prompt Rules**: Keeps the additional pulled field visible by default and hides it dynamically when the specified condition is met.
Where Pull From fields are supported as trigger inputs, additional Pull From fields can now be used directly in condition statements (for example: *"Show Inspection Checklist if Pulled Asset Category equals 'Heavy Machinery'"*), utilizing standard comparison operators for that field’s data type.
* **Real-Time Dynamic Evaluation**: Visibility conditions update instantly as users make selections on the form without requiring page reloads or form resets. If a parent Pull From selection changes, all dependent additional pulled fields and their associated Show/Hide conditions re-evaluate in real time.
* **Smart Required-Field Validation**: Form submission validation automatically adapts to field visibility. If an additional pulled field is configured as required but is currently hidden by a Show/Hide rule, it will not block form submission. Once visible, standard required-field validation applies before submission.
* **Preserves Field Configurations & Permissions**: Dynamic visibility strictly respects underlying field settings, including read-only statuses, default values, user permissions, and parent collection dependencies.
* **Seamless Backward Compatibility**: Existing forms and Pull From fields continue to function without any required configuration updates. Additional Pull From fields remain visible by default unless a new Show/Hide rule is explicitly added.
* **Full Multi-Platform Support**: Dynamic show/hide behavior for additional pulled fields works consistently across the **Web** platform and both **iOS and Android** companion apps.
### Export Images as Embedded Files in Excel and PDF Reports
We have enhanced our export engine to support embedded images, allowing teams to include photos, inspections, barcodes, and signature images directly inside exported Excel (`.xlsx`) spreadsheets and PDF reports rather than exporting raw URLs or text placeholders. This functionality is ideal for creating shareable asset catalogs, field inspection summaries, insurance documentation, and equipment sign-off sheets that require visual proof without opening external browser links.
* **Direct In-Cell Image Embedding**: When exporting records to Excel (`.xlsx`), images from photo and attachment fields embed directly into their corresponding table cells.
* **Flexible Export Settings**: Administrators and users can choose whether images are embedded during export or displayed as clickable hyperlinks that point to the high-resolution file in Asset Panda Pro.
* **Support for Multiple Media & Field Types**: Works across single image fields, multi-image galleries, captured signatures, barcode snapshots, and thumbnail previews of uploaded image attachments.
* **Automatic Cell Sizing & Aspect Ratio Preservation**: Images scale within table rows and columns, preventing distortion, stretching, or cell overlap across large multi-row spreadsheets.
* **High-Resolution PDF Rendering**: When generating PDF reports or record summaries, embedded photos render visuals optimized for both on-screen viewing and physical printouts.
* **Optimized Performance for Large Datasets**: Bulk exports process in the background with progress indicators, ensuring smooth file generation without browser freezing.
* **Cross-Platform Availability**: Export reports with embedded images seamlessly from the web platform and save or share generated reports directly from iOS and Android companion apps.
***
## Integrations
### Integration syncs built into Mappings
Syncs can now be managed directly from the mapping screen, without navigating to a separate Automation page.
* **Run Syncs On Demand:** Trigger any integration sync manually from the mapping page.
* **Sync Visibility:** View which sync is associated with which mapping.
* **Detailed View:** Access a clear, consolidated view of each mapping's sync activity.
* **Centralized Management:** Enable, disable, run, and view logs for syncs from a single page.
* **Multiple Mappings, One View:** Manage syncs across all mappings for an integration.
### Reliable automation triggers for integration syncs
Automations can now be triggered by records created and updated through an integration sync, rather than by updates alone.
* **Create and Update Support:** Integration as a trigger source now supports both update and create triggers.
* **Consistent Behavior:** Integration-driven changes are separated from automation-driven changes internally, resolving prior inconsistencies in trigger behavior.
* **Applicable Use Cases:** Send a notification when new records are added via sync, initiate downstream workflows (tasks, tickets, related records) when a sync creates data, and keep collections synchronized regardless of whether the source data is new or updated.
* **Usage:** Open the automation, go to **WHEN**, select **When a record is created** or **When a record is updated**, select **Integration** under **By**, select the collection, then add conditions and actions.
Note: If **Integration** is not selected under **By**, the automation will not trigger for records introduced through a sync.
### Integration sync logs
Integration sync runs now have their own dedicated log, separate from Automation logs. Integration sync logs are now available as a separate option under **Tools ›** **Activity Stream**.
### Jobber Integration
The first iteration of the Jobber integration is available: inbound sync for Jobs and Properties. Job and Property records now sync automatically from a connected Jobber account into Asset Panda Pro.
* **Delta Sync:** Data stays current on a regular schedule via delta sync - no full re-pull every cycle. (Property sync is a full load.)
* **Field Mapping:** Admins can map Jobber fields to Asset Panda Pro fields during setup.
* **Filtered Sync:** Admins can filter which records sync in.
* **Custom Field Mapping:** Custom fields from jobs can be mapped and later we be able to be used to send the asset link back to Jobber (future scope).
See [Jobber integration](/integrations-store/ticket-management/jobber-integration.md).
### **Freshservice Integration: Bi-directional Sync**
Ticket updates, including status, priority, assignment, custom fields, and more, can now be pushed from Asset Panda Pro to Freshservice.
* **Ticket Write-Back:** **Service Write-Back:** Write-back is supported for Services and for Business, IT, Sales, and Support Service records.
* **Per-Field Sync Direction:** A new setting in field mapping lets admins choose pull, push, or both for each field.
* **Automatic Alignment:** Once mappings are configured, Asset Panda Pro keeps both systems in sync automatically, removing the need to update Freshservice separately.
See [Freshservice integration](/integrations-store/ticket-management/freshservice-integration.md).
### **Workday Integration: Location and Cost Center Inbound Sync**
Location and Cost Center records can now be synced from Workday into Asset Panda Pro.
* **Organizations API:** Location and Cost Center data are pulled from Workday's Organizations API, filtered by organization type.
* **Consistent Records:** Employee and asset records stay aligned with the Workday organizational structure.
Note: This integration uses a single unified sync (Organizations) rather than two separate syncs. Use the organization type field to retrieve Cost Center or Location records.
See [Workday integration](/integrations-store/operations-ops/workday-integration.md).
### **Kandji Integration: Two-Way Sync**
Asset Panda Pro updates can now be pushed to Kandji:
* **Device Write-Back:** Device updates can now be pushed to Kandji and filtered by Asset Tag, Blueprint, Tags, and all other supported fields.
* **Per-Field Sync Direction:** A new setting in field mapping lets admins choose pull, push, or both for each field.
* **Separate Write-Back Logging:** Write-back activity appears in sync logs separately from pull activity.
See [Kandji integration](/integrations-store/device-management/kandji-iru-integration.md).
### **Cisco Meraki Integration: Two-Way Sync**
Asset Panda Pro updates can now be pushed to Cisco Meraki.
* **Supported Entities:** Administrators, Network Clients, Network Devices, Networks, and Organization Devices
* **Separate Mapping:** Two-way sync requires a separate mapping, so existing inbound syncs are unaffected.
* **Centralized Management:** Teams managing network infrastructure can keep Meraki and Asset Panda Pro aligned from one place, instead of updating both systems manually.
See [Cisco Meraki integration](/integrations-store/device-management/cisco-meraki-integration.md).
### **ConnectWise Integration: Two-Way Sync**
Asset Panda Pro updates can now be pushed to ConnectWise.
* **Supported Entities:** Agreement, Company, Configuration, Contact, and Site
* **Field Support:** Any field supported by the ConnectWise API is available for write-back
* **Separate Mapping:** Two-way sync requires a separate mapping, so existing inbound syncs are unaffected.
* **Centralized Management:** Teams managing company, site, and contact records can keep ConnectWise and Asset Panda Pro aligned from one place, instead of updating both systems manually.
See [ConnectWise integration](/integrations-store/data-sync/connectwise-integration.md).