> ## Documentation Index
> Fetch the complete documentation index at: https://smartcar.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Configure Permissions for Vehicle Data Collection

> Step-by-step guide to selecting signals, commands, and attributes in the Smartcar Dashboard and requesting the right permissions from vehicle owners.

To retrieve vehicle data through Smartcar, you must configure your application to request the correct permissions from vehicle owners. This guide walks you through the process using the Smartcar Dashboard.

<Steps>
  <Step title="Open the Configuration Page in the Dashboard">
    Go to the [Smartcar Dashboard](https://dashboard.smartcar.com/configuration) and select your application. Navigate to the <b>Configuration</b> section and choose the <b>Vehicle access</b> tab.
  </Step>

  <Step title="Select Signals, Commands, and Attributes">
    Under the <b>Signals</b>, <b>Commands</b>, and <b>Attributes</b> tabs, select the specific vehicle data points and actions your application needs. Each selection corresponds to a permission that the vehicle owner must approve.

    <Frame type="simple" caption="Application Configuration in Smartcar Dashboard">
      <img src="https://mintcdn.com/smartcar-docs/YqcNJdgEDgXpXtEG/images/how-to/vehicle-access.png?fit=max&auto=format&n=YqcNJdgEDgXpXtEG&q=85&s=8dbd5a5cbf7561ce6890e8b74d2e3af1" alt="Smartcar Dashboard configuration page showing signal selection and Connect Preview." width="5014" height="2966" data-path="images/how-to/vehicle-access.png" />
    </Frame>

    <ul>
      <li><b>Signals:</b> Dynamic vehicle data (e.g., battery level, odometer, location).</li>
      <li><b>Commands:</b> Actions your app can perform (e.g., lock/unlock, start charging).</li>
      <li><b>Attributes:</b> Static vehicle info (e.g., make, model, year).</li>
    </ul>

    <Note>
      Only select the permissions your application truly needs. This improves user trust and increases the likelihood of successful connections.
    </Note>
  </Step>

  <Step title="Preview the Owner Experience">
    As you select signals, commands, and attributes, the <b>Connect Preview</b> on the right updates to show what the vehicle owner will see when connecting their vehicle. This preview lists the permissions your app is requesting and the vehicles that will be connected.
  </Step>

  <Step title="Publish Your Configuration">
    Once you are satisfied with your selections, click <b>Publish</b> to save your configuration. Your application will now request these permissions from vehicle owners during the Smartcar Connect flow.
  </Step>
</Steps>

## Dynamic Permissions

If your application needs to access different permissions based on user actions or vehicle types, you can leverage the `scope` parameter in the Smartcar Connect URL to dynamically request permissions at runtime. This allows you to tailor the permissions based on the specific vehicle or user context.
Keep in mind that any permissions you pass via the `scope` parameter will override the permissions configured in the Smartcar Dashboard for that specific connection.

### Notes

* If you need to change permissions later, you can return to this configuration page and update your selections. Vehicle owners will need to reauthorize your application to grant any new permissions.
* The permissions you select here will determine the data and actions available to your application. Make sure to choose only what is necessary for your use case.

## Mark Permissions as Required or Optional

<Note>
  **Effective June 16th, 2026.** The behavior described in this section takes effect on June 16th, 2026.
</Note>

In the **Vehicle Access** tab, each signal has a **Required** toggle that controls how its permission appears to vehicle owners on the Connect grant screen.

* **Required** (toggle on): the permission appears checked and locked. The vehicle owner cannot uncheck it.
* **Optional** (toggle off): the permission appears checked by default, and the vehicle owner can uncheck it before connecting.

<Frame type="simple" caption="The Required toggle in the Dashboard's Vehicle Access tab.">
  <img src="https://mintcdn.com/smartcar-docs/AnN7ZGCKcf4tY_kc/images/how-to/vehicle-access-required-toggle.png?fit=max&auto=format&n=AnN7ZGCKcf4tY_kc&q=85&s=90bbf4782454c00394b364321e0d5b16" alt="Smartcar Dashboard Vehicle Access tab with the Required toggle on for Amperage and Amperage Max and off for other Charge signals." width="1530" height="1166" data-path="images/how-to/vehicle-access-required-toggle.png" />
</Frame>

At least one permission must remain selected for the owner to complete the connection.

Only mark a permission as required if it is absolutely necessary for your application to function. Leaving non-essential permissions optional gives vehicle owners more control and can improve your connection rate.

<Note>
  Marking a permission as required signals that your application needs it. It does not guarantee the vehicle supports it. To restrict which vehicles can connect by powertrain type, use [Connection Filters](/connect/advanced-config/connection-filters).
</Note>

***

## What’s Next

* [How to Connect Vehicles](/getting-started/connect-vehicles)
* [How to Manage API Tokens](/getting-started/how-to/manage-api-tokens)
* [API Reference: Permissions](/api-reference/permissions)