Settings Reports provide a fleet-wide view of how settings are applied across all assets, helping you confirm configurations and enforce policies. Instead of checking each vehicle individually, you can use pre-built or custom reports to audit settings across thousands of assets, identify manual overrides, and spot misconfigurations.
Templates are the quickest way to audit settings across your fleet. To build a Settings Report from a template, follow this workflow:
-
From the Samsara dashboard, navigate to Reports (
).
-
Select View all templates at the top right.
-
Scroll down and choose from one of the following templates:
-
Settings Overrides Audit: Identify assets with at least one manually overridden setting to see which asset configurations differ from organizational defaults.
-
Safety Settings Overview: View fleet-wide safety settings like seat belt detection or mobile usage alerts for every asset in your fleet.
-
-
Review the generated report and customize it as desired.
You can customize the time range, add filters, sort, and group by custom fields, and add, edit, reorganize, or delete columns.
-
Click Save.
You can create your own Settings Report by adding settings fields to any Advanced Custom Report. This is useful for deeper auditing or troubleshooting. For example, you can verify that a specific setting is enabled for every vehicle in your fleet, or flag which vehicles have multiple settings overrides for additional review.
To manually create a Settings Report, follow this workflow:
-
From the Samsara dashboard, navigate to Reports (
-
Click New Report.
-
Select the Assets dataset, then click Use Dataset to create a custom report with this dataset.
-
To add settings fields to your report, click Add Column (
).
Filter the list to settings fields by typing
Setting:in the Search Fields box. See Types of Settings Fields for the types of settings fields that are available, and Supported Features for the different features that can be audited. -
Select one or more settings fields and add them to your report.
-
(Optional) Filter the report for additional insights on how settings are being used in your organization. Some example filters you can apply include:
-
Setting: Mobile Usage Alert - Applied From contains Assetto display all assets where the Mobile Usage Alert setting is customized at the asset level. This helps you quickly identify which assets deviate from the organizational default for that specific setting. -
Settings from Asset > 0to display all assets that have one or more settings overrides. This helps you identify assets that deviate from organizational defaults or have a high number of customized settings applied.
-
-
Enter a name for the custom report.
A name is required to save and share the report.
-
Click Save.
-
After the report is saved, to refresh the custom report data you can click Run Report.
Note
Larger reports may take several minutes to load. If the report has too much data, the report may not successfully run. Try adjusting or removing filters, adjusting the date range, or removing columns from the report.
-
After saving the report, it will appear in the list of Custom Reports (Reports (
When you click Add Column () in a Settings Report, you can search for available settings fields by entering the prefix
Setting:
These settings fields help you analyze how specific configuration settings are applied across your fleet. You can add the following fields to a report:
-
Setting Value: Whether a setting is On, Off, or set to a specific numeric value
-
Setting Source: Where the setting is configured, whether from an organization default or asset-level override.
-
Setting Detail: How many settings have been manually overridden on the asset and a direct link to the asset page.
Refer to the sections below for more information and examples of these types of settings fields.
Adding a setting value field to your report can help you identify whether a setting is On or Off, or check the numeric value for configurable settings like speed thresholds or notification limits. These fields use the format Setting: [Setting Name].
For example, adding the Setting: Inattentive driving detection field to your report will indicate whether inattentive driving detection is enabled or disabled for each vehicle in the report.
This is useful for identifying when vehicle or asset settings deviate from the expected org default, or to confirm that a setting override has been applied as expected. In the example below, TRUCK 3 is the only vehicle in the report with inattentive driving turned Off.
Other examples of setting value fields include:
|
Setting Value Field |
Example Value |
Description |
|---|---|---|
|
Setting: Eating detection |
On |
Eating detection is enabled for the vehicle’s inward-facing dash cam. |
|
Setting: Detect pedestrian collisions on rear camera |
Off |
Pedestrian detection is turned off for the rear-facing camera. |
|
Setting: Drowsiness detection nudges alert count threshold |
2 |
Two in-cab alerts are triggered before a drowsiness event is logged. |
|
Setting: Trip Start Speed Threshold |
5 |
The trip begins automatically when vehicle speed exceeds 5 mph (or km/h, depending on your org locale). |
Adding a setting source field to your report can help you understand where the setting is being applied—either the organization default or at the asset level. These fields use the format Setting: [Setting Name] - Applied From.
For example, adding the Setting: Inattentive driving detection - Applied From field to your report will indicate where inattentive driving has been configured for each vehicle in the report. In the example below, TRUCK 3 has inattentive driving turned Off because the setting has been overridden at the Asset level, while the other vehicles are inheriting the Org Default.
Other examples of setting source fields include:
|
Setting Source Field |
Example Value |
Description |
|---|---|---|
|
Setting: Eating detection - Applied From |
Org Default |
The eating detection setting is being applied from the default organization configurations. |
|
Setting: Detect pedestrian collisions on rear camera - Applied From |
Asset |
The rear camera pedestrian collision detection is being applied by a setting override at the asset level. To get a direct link to the asset details page where the setting is configured, you can also add the |
Adding a setting detail field to your report can help you identify how many settings overrides are applied to assets and get a direct link to the page where these overrides are being applied.
The following setting detail fields can be added to a Settings Report:
-
Number of settings overrides: This field uses the format
Settings from Asset. Adding this to your report will indicate how many settings are being overridden for each vehicle in the report. This can help you verify whether vehicles in the fleet have the expected number of overrides. In the example below, TRUCK 3 is the only asset with three settings overrides applied.By applying report filters to the
Settings from Assetfield, you can also identify vehicles that have more or fewer settings overrides than expected. -
Link to asset settings page: This field uses the format
Settings URL. Adding this to your report will provide a link to the asset details page, where you can view all settings currently applied to each vehicle in the report.
Settings Reports enable you to audit a variety of camera, gateway, and safety configurations in your fleet. The following table summarizes which features and hardware have auditable settings:
|
Category |
Available Settings |
|---|---|
|
Cameras |
|
|
Connected Equipment |
|
|
Device Health |
|
|
Safety Events |
|
|
Telematics |
|
Comments
0 comments
Article is closed for comments.