# Customizing Connect Webviews You can use [Seam Console](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/core-concepts/seam-console) to customize the [Connect Webviews](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/core-concepts/connect-webviews) that you present to your users through your app. You can customize the following characteristics of your Connect Webviews: * [Look and feel](#customize-the-look-and-feel-of-your-connect-webviews) * [Brands (manufacturers) to display](#customize-the-brands-to-display-in-your-connect-webviews) * [Behavior settings](#customize-the-behavior-settings-of-your-connect-webviews), including `automatically_manage_new_devices` and `wait_for_device_creation` *** ## Customize the Look and Feel of Your Connect Webviews You can customize the look and feel of your Connect Webviews in the following ways: * **Inviter name:** Define the name to display in your Connect Webviews as the entity requesting user authorization for Seam to access their device or access control system account. * **Logo:** Choose a logo for your Connect Webviews. Ensure that the image file size does not exceed 1 MB. * **Logo shape:** Select the shape of your logo displayed in Connect Webviews. Choices are **Circle** (default) or **Square**. * **Primary button style:** Customize the background and text colors of the action button in your Connect Webview flow using a hex color code. The default color is #232426, which is almost black, and the default text color on the button is white. * **Success message:** Customize the message that the Connect Webview displays when the connection completes successfully. It is important to note that any changes you make to the customization features will apply to all of your new Connect Webviews.
You can customize the look and feel of Connect Webviews.

You can customize the look and feel of Connect Webviews.

To customize the look and feel of your Connect Webviews: 1. In the top navigation pane of [Seam Console](https://console.seam.co/), click **Developer**. 2. In the left navigation pane, click **Webviews**. 3. On the **Webviews** page, click **Configure your webview**. 4. In the **Customize your Webview** pane, configure any of the following features:
FeatureInstructions
Inviter name
  1. In the Inviter Name area, click Edit.
  2. Type the desired inviter name and then click Save.
Logo
  1. In the Logo area, click Upload new logo.
  2. Navigate to and select the image file that contains the desired logo.
    The image file size cannot exceed 1 MB.
  3. Click Open.
Logo shape
  1. In the Logo Shape area, click Edit.
  2. Select Circle or Square and then click Save.
Primary button style
  1. In the Primary Button Style area, click Edit.
  2. Click the Button Background Color field and specify the desired color. Default: #232426 (almost black).
  3. Click the Button Text Color field and specify the desired color. Default: #ffffff (white).
  4. Click Save.
Success message
  1. In the Success Message area, click Edit.

  2. In the Message field, type the desired success message.

    To reset the success message, click Clear.

  3. Click Save.
*** ## Customize the Brands to Display in Your Connect Webviews When you create a Connect Webview, you can customize the providers—that is, the brands—that it displays. In the [Create Connect Webview](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/api/connect_webviews/create) request, include the desired set of device provider keys in the `accepted_providers` parameter. Seam supports the following device provider keys: | Provider Name | Device Provider Key | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | | [2N](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/2n-intercom-systems) | `my_2n` | | [4SUITES](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/4suites-locks) | `four_suites` | | [Akiles](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/akiles-locks) | `akiles` | | [Akuvox](https://akuvox.com/) | `akuvox` | | [ASSA ABLOY Credential Service](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/assa-abloy-credential-services) | `assa_abloy_credential_service` | | [ASSA ABLOY Visionline Access Control System](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/assa-abloy-visionline-access-control-system) | `visionline` | | [August Home](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/august-locks) | `august` | | [Avigilon Alta](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/avigilon-alta-access-system) | `avigilon_alta` | | [Brivo](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/brivo-access) | `brivo` | | [ControlByWeb](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/get-started-with-controlbyweb-devices) | `controlbyweb` | | [DoorKing](https://www.doorking.com/) | `doorking` | | [dormakaba Oracode](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/dormakaba-oracode-locks) | `dormakaba_oracode` | | [ecobee](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/ecobee-thermostats) | `ecobee` | | [Genie Aladdin Connect](https://www.geniecompany.com/aladdin-connect-by-genie) | `genie` | | [Honeywell Resideo](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/honeywell-thermostats) | `honeywell_resideo` | | [igloohome](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/igloohome-locks) | `igloohome` | | [Kwikset](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/kwikset-locks) | `kwikset` | | [Latch](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/latch-access-control-system) | `latch` | | [Linear](https://linear-solutions.com/) | `linear` | | [Lockly](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/lockly-locks) | `lockly` | | [Minut](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/minut-sensors) | `minut` | | [Nest](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/google-nest-thermostats) | `google_nest` | | [NoiseAware](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/noiseaware-sensors) | `noiseaware` | | [Nuki](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/nuki-locks) | `nuki` | | [PTI Storlogix Cloud](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/pti-storlogix-cloud) | `pti` | | [Salto KS Access System](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/salto-ks-access-control-system) | `salto_ks` | | [Salto KS Locks](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/salto-locks) | `salto_ks` | | [Salto ProAccess Space Access System](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/salto-proaccess-space-access-system) | `salto_space` | | [Schlage](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/schlage-locks) | `schlage` | | [Sensi](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/sensi-thermostats) | `sensi` | | [SmartThings](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/get-started-with-smartthings-hubs-+-smart-locks) | `smartthings` | | [Tedee](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/tedee-locks) | `tedee` | | [TTLock](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/ttlock-locks) | `ttlock` | | [Wyze](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/wyze-locks) | `wyze` | | [Yale](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/device-and-system-integration-guides/yale-locks) | `yale` | To help you decide which providers to include in a Connect Webview, you can use the [List Device Providers](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/api/devices/list_device_providers) method to learn about each provider. The information that this method returns for each provider includes a set of [capability flags](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/capability-guides/device-and-system-capabilities#capability-flags), such as `device_provider.can_remotely_unlock`. If at least one supported device from a provider has a specific capability, the corresponding capability flag is `true`. {% hint style="info" %} If you omit the `accepted_providers` parameter, the Connect Webview displays all of the stable providers that Seam supports, by default. For more information about provider categories, see [Step 1: Create a Connect Webview](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/core-concepts/connect-webview-process#step-1-create-a-connect-webview). {% endhint %} The following Connect Webview creation request specifies that the Connect Webview should only display August and Schlage: {% tabs %} {% tab title="Python" %} **Request:** ```python seam.connect_webviews.create( accepted_providers = ["august", "schlage"] ) ``` **Response:** ``` ConnectWebview( connect_webview_id='1139e5a5-4bfd-4c78-9a89-83a439ad538e', status='pending', url='https://connect.getseam.com/connect_webviews/view?connect_webview_id=1139e5a5-4bfd-4c78-9a89-83a439ad538e&auth_token=5g6Nt1sunJamS1huj7pwztKaMaBpvKhLc', accepted_providers=[ 'august', 'schlage' ], ... ) ``` {% endtab %} {% tab title="cURL (bash)" %} **Request:** ```bash curl -X 'POST' \ 'https://connect.getseam.com/connect_webviews/create' \ -H 'accept: application/json' \ -H 'Authorization: Bearer ${API_KEY}' \ -H 'Content-Type: application/json' \ -d '{ "accepted_providers": [ "august", "schlage" ] }' ``` **Response:** ```json { "connect_webview": { "connect_webview_id": "1139e5a5-4bfd-4c78-9a89-83a439ad538e", "status": "pending", "url": "https://connect.getseam.com/connect_webviews/view?connect_webview_id=f5fa50b8-b7e3-45ed-b636-354c17df5d8a&auth_token=6w2tZqeYN4xEYcMf8ySsGgpwFAQgET6Lb", "accepted_providers": [ "august", "schlage" ], ... }, "ok": true } ``` {% endtab %} {% tab title="JavaScript" %} **Request:** ```javascript await seam.connectWebviews.create({ accepted_providers: ["august", "schlage"] }) ``` **Response:** ```json { connect_webview_id: '1139e5a5-4bfd-4c78-9a89-83a439ad538e', status: 'pending', url: 'https://connect.getseam.com/connect_webviews/view?connect_webview_id=8cf491d8-cf67-4ad0-907d-3a8ae3764019&auth_token=C4vLHdKqpMavg6HYBbejQkE1dZ8KDcetS', accepted_providers: [ 'august', 'schlage' ], ... } ``` {% endtab %} {% tab title="Ruby" %} **Request:** ```ruby client.connect_webviews.create( accepted_providers: ["august", "schlage"] ) ``` **Response:** ``` ``` {% endtab %} {% tab title="C#" %} **Request:** ```csharp List acceptedProviders = new() { Seam.Api.ConnectWebviews.CreateRequest.AcceptedProvidersEnum.August, Seam.Api.ConnectWebviews.CreateRequest.AcceptedProvidersEnum.Schlage }; seam.ConnectWebviews.Create( acceptedProviders: acceptedProviders ); ``` **Response:** ```json { "connect_webview_id": "f69fa3b8-c89d-4fd4-b6fc-feb456d07234", "status": "pending", "url": "https://connect.getseam.com/connect_webviews/view?connect_webview_id=f69fa3b8-c89d-4fd4-b6fc-feb456d07234&auth_token=MCh7Vm2fnvyiPhtjB8Lemqr93aeHXhJhM", "accepted_providers": [ "august", "schlage" ], ... } ``` {% endtab %} {% tab title="Java" %} **Request:** ```java seam.connectWebviews().create(ConnectWebviewsCreateRequest.builder() .acceptedProviders(List.of( AcceptedProvider.AUGUST, AcceptedProvider.SCHLAGE)) .build()); ``` **Response:** ```json { "connect_webview_id" : "172c1d65-8904-4d43-9eee-099780ba6558", "status": "pending", "url" : "https://connect.getseam.com/connect_webviews/view?connect_webview_id=172c1d65-8904-4d43-9eee-099780ba6558&auth_token=7hpz4wGsaphJmBcs2TKr4H3ZkGgmqpPma", "accepted_providers" : [ "august", "schlage" ], ... } ``` {% endtab %} {% endtabs %} *** ## Customize the Behavior Settings of Your Connect Webviews You can use the following two properties to customize the behavior of your Connect Webviews: * [`automatically_manage_new_devices`](#automatically_manage_new_devices) * [`wait_for_device_creation`](#wait_for_device_creation) You configure these properties when you are creating the Connect Webview. Consequently, you can customize these two characteristics for each of your Connect Webviews. ### `automatically_manage_new_devices` Seam charges fees for different parts of the API, like connecting a device, creating an access code or thermostat schedule, and creating an access control system user. To learn more, contact our team. You can exclude specific devices from your bill by marking them as "[unmanaged](https://docs.seam.co/latest/~/revisions/DFdrUdS2jQOnbJTNDT5a/core-concepts/devices/managed-and-unmanaged-devices)." The default value for `automatically_manage_new_devices` is `true`. Consequently, by default, Seam imports all devices and makes them available for use. However, if you set this property to `false`, Seam sets the `is_managed` property for all new devices to `false` (that is, unmanaged) when a user first connects their account to Seam. ### `wait_for_device_creation` This property enables you to specify whether Seam should finish syncing all devices in a newly-connected account before completing the associated Connect Webview. The default value for `wait_for_device_creation` is `false`. If `wait_for_device_creation` is `false`, you should wait for `connected_account.completed_first_sync` before retrieving your devices. This event indicates that Seam has finished the first sync of the connected account, and the connected devices are available. Alternately, if you set `wait_for_device_creation` to `true`, Seam finishes syncing all devices in the newly-connected account before proceeding to the final page of the Connect Webview. In this case, you can fetch your devices immediately upon the completion of the Connect Webview.