> ## Documentation Index > Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Schneider Access Expert > Connect Schneider Access Expert to KODE OS for access control data > Connect Schneider Access Expert to KODE OS for access control data integration ## Overview Use this integration to connect Schneider Access Expert (AccessXpert) to KODE OS. You can discover access devices and points, then monitor entries, exits, and access attempts for operations and reporting. | Property | Value | | ------------------- | -------------- | | **System Type** | Access Control | | **Communication** | REST | | **Collection** | Pull | | **Collection Mode** | SNAPSHOT | ## Supported Capabilities * Discover Devices & Points * Collect Sensor Data * Collect Non-Sensor Data ## Prerequisites * An active account with Schneider Access Expert and access to their API or developer portal * Username and password credentials for the Schneider Access Expert system * KODE OS environment with access to Data Sources ## Configure Connector in KODE OS 1. Navigate to **Data Sources** in your building 2. Click **API Catalog** and search for **Schneider Access Expert** 3. Click **+ Add Datasource** 4. Fill in the fields below and complete the three-page setup flow | Field | Required | Type | Description | | ------------ | -------- | -------- | -------------------------------------------------------- | | **URL** | Yes | text | The base URL or IP address of the external system | | **Instance** | Yes | text | The instance name or number in the external system | | **Username** | Yes | text | The username for authenticating with the external system | | **Password** | Yes | password | The password for authenticating with the external system | ## Discover Devices and Points After configuring the connector, click **Discover** on the connector detail page. KODE OS will query the Schneider Access Expert system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the [Discovery guide](/products/integrations/capabilities/discovery). ## Devices and Points When you discover devices from Schneider Access Expert, KODE OS maps them to the following device types and data points: ### Access Controller Canonical Type: `default` | # | Point | Description | Unit | Writable | Collection | | -- | ----------------------- | ------------------------------------------------------------------------------------- | ---- | -------- | ---------- | | 1 | `is_tampered` | **True** -- is\_tampered is active / **False** -- is\_tampered is not active | -- | No | Polling | | 2 | `door_forced_open` | **True** -- door has been forced open / **False** -- no forced entry detected | -- | No | Polling | | 3 | `mask_door_forced_open` | **True** -- door has been forced open / **False** -- no forced entry detected | -- | No | Polling | | 4 | `door_held_open` | **True** -- door is being held open / **False** -- door is not held open | -- | No | Polling | | 5 | `mask_door_held_open` | **True** -- door is being held open / **False** -- door is not held open | -- | No | Polling | | 6 | `door_contact_faulted` | **True** -- fault condition detected / **False** -- no fault | -- | No | Polling | | 7 | `rex_faulted` | **True** -- fault condition detected / **False** -- no fault | -- | No | Polling | | 8 | `latch_mode` | Current latch operating mode | -- | No | Polling | | 9 | `entry_delay` | Entry delay timer duration | -- | No | Polling | | 10 | `exit_delay` | Exit delay timer duration | -- | No | Polling | | 11 | `debounce` | Debounce timer setting | -- | No | Polling | | 12 | `behaviour` | Configured device behaviour | -- | No | Polling | | 13 | `hold_time` | Hold time duration setting | -- | No | Polling | | 14 | `is_disabled` | **True** -- device is disabled / **False** -- device is enabled | -- | No | Polling | | 15 | `is_online` | **True** -- device is connected and reporting / **False** -- device is not responding | -- | No | Polling | | 16 | `is_powered` | **True** -- is\_powered is active / **False** -- is\_powered is not active | -- | No | Polling | | 17 | `is_faulted` | **True** -- fault condition detected / **False** -- no fault | -- | No | Polling | | 18 | `is_battery_low` | **True** -- battery is OK / **False** -- battery needs attention | -- | No | Polling | | 19 | `mode` | Current operating mode | -- | No | Polling | | 20 | `activation_time` | Activation time duration | -- | No | Polling | | 21 | `is_activated` | **True** -- device is activated / **False** -- device is not activated | -- | No | Polling | ## What Data You Get ### Point History Time-series readings including is\_tampered, door\_forced\_open, mask\_door\_forced\_open, door\_held\_open, mask\_door\_held\_open, door\_contact\_faulted, rex\_faulted, latch\_mode, and 13 more, collected at regular intervals from connected devices ### Event Logs System and security event records with timestamps, event types, and associated devices KODE OS maps Schneider Access Expert data to these standard fields: | KODE Field | Source Field | Notes | | ---------------- | ------------------------------ | ----------- | | **category** | `EventCategory.ACCESS_CONTROL` | -- | | **id** | `key` | -- | | **name** | `messageShort` | -- | | **description** | `messageLong` | -- | | **deviceId** | `clientDeviceId` | -- | | **createdAt** | `occurredOn` | transformed | | **customFields** | `priority` | -- | ### Access Control Access control records including card reader events, credential verification, and zone access KODE OS maps the collected data to these standard fields: | KODE Field | Description | | ------------------- | ----------------------------------------------- | | **ID** | Unique log entry identifier | | **Description** | Event description | | **Person Name** | Name of the person involved | | **Credential ID** | Badge or credential identifier used | | **Credential Type** | Type of credential (e.g., Card, PIN, Biometric) | | **Role** | Access role or clearance level | | **Type** | Event type (e.g., Entry, Exit, Denied) | | **Result** | Access result (Granted, Denied, Error) | | **Access Point** | Door or access point name | | **Location** | Physical location of the access point | | **Access Time** | Timestamp of the access event | | **Created At** | Timestamp when the log was recorded | ### Polling Schedule * **Point History** -- Default polling: 1 minutes (min: 1 minutes, max: 1 hours) * **AccessControl** -- Default polling: 5 minutes (min: 5 minutes, max: 5 minutes) * **EventLog** -- Default polling: 1 days (min: 1 days, max: 1 days) For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection). ## Use Cases Once connected, this integration enables you to: * Centralize access event monitoring across all entry points and zones * Generate audit trails for security compliance and investigation * Correlate access patterns with occupancy and energy data for building optimization ## Troubleshooting Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Verify the username and password are correct and the account has not been locked in the Schneider Access Expert system. Verify the connector credentials have sufficient permissions in the Schneider Access Expert system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration. Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Schneider Access Expert API.