Skip to main content

​
Updating access with Tesla

You can use either of the following URLs to prompt users for more Tesla permissions in the event you need additional access from the vehicle owner due to: If one or more of the Smartcar scopes you pass map to a new Tesla permission(s) for the account, the user will be prompted to update access after they log in with Tesla. To prompt users to update their Tesla permissions, use the reauthentication flow. This allows users to grant additional permissions without requiring a new vehicle connection.
The reauthentication flow does not redirect the user back to your application or issue new credentials. Your existing application-level access token continues to work for all connected vehicles.

​
Requiring Tesla Permissions

To ensure users select the necessary permissions with Tesla before being able to connect their vehicle via Smartcar, please append the required: prefix to Smartcar scopes in your Connect URL e.g. required:read_location. As a result if they do not select the necessary permissions with Tesla, they will see the following screen and be prompted to return to Tesla to update their permissions.

​
Permission Mappings

Tesla provides a limited set of permissions. To ensure vehicle data is shared only with explicit consent, Smartcar has mapped Tesla’s permissions into its existing more granular options. For example, granting access to “vehicle commands” in a Tesla account allows an application to start or stop charging, lock or unlock doors, enable or disable Sentry Mode, and more. Smartcar separates these permissions so that applications must request access to control charging separately from access to vehicle security, control navigation, etc. Smartcar does not use or share vehicle data beyond the permissions listed in this table. An application with the ability to control the charge status of a vehicle, does not have access to control other aspects of the car unless explictly requested and granted by a vehicle owner.