Skip to main content

Post-Deployment Configuration

Your deployment comes up working, but a few things only you can supply: who administers it, credentials for the third-party services you want to integrate, and which optional node capabilities to allow. Work through this page once, immediately after deploying.

1. Sign in as an administrator​

The accounts you listed in AdminEmails at deploy time already exist as super admins. A single one-time password is generated for them. You can find the dashboard URL and the temporary password in the Installer Dashboard.

You are required to change it at first sign-in.

2. Voice assistants​

In the Admin Dashboard, under Settings → Voice assistants, there are separate Alexa and GVA tabs. Each needs credentials from a skill or project you have registered with the vendor — that account and its review process belong to you.

You only need this if you want voice control; skip it otherwise, and the rest of the deployment is unaffected. See Voice assistants for what the integration gives you.

3. Push notification credentials​

Under Settings → Push notifications, supply the APNs and FCM credentials for your phone app. Until you do, notification events are generated and have nowhere to be delivered.

4. Custom domain​

The dashboard and APIs come up on generated AWS hostnames. To put them behind your own domain you need a certificate in the right region and the corresponding deployment parameters set — this is a deploy-time input rather than a dashboard setting, so plan it before you go live rather than after.

5. Optional node capabilities​

Some capabilities attach extra server-side permissions to a node and are therefore opt-in per registration batch, under Choose capabilities when you register nodes:

  • File Storage (S3) — device-uploaded files
  • Camera Streaming (KVS) — video streams

Enable only what your firmware actually uses. Each one widens what a compromised node could reach.