Skip to main content

Getting Started

Welcome to ioX-Pulse. This guide walks you through the first 30 minutes after your partner account is created, from signing in for the first time to watching your first device send live data.

note

This page is for Partner Admins setting up a new workspace. If you're a user being added to an existing workspace, skip to Step 1 and your admin will have done the rest.

What you'll need​

  • The invitation email sent to you when your account was created.
  • A LoRaWAN device with its DevEUI and AppKey to hand, printed on the device, its packaging, or supplied by the manufacturer.
  • A LoRaWAN gateway online and within range of the device. If you don't have one connected yet, see Gateway setup first.
  • An authenticator app on your phone (Google Authenticator, Authy, 1Password, Microsoft Authenticator) if your workspace requires multi-factor authentication.
  • About 30 minutes.

Step 1: Sign in for the first time​

Open the invitation email and click Accept invite. You'll be taken to ioX-Pulse to set up your password.

  1. Choose a password: at least 12 characters, with at least one uppercase letter, one lowercase letter, and one number. Passwords that have appeared in known data breaches are rejected, so pick something you don't use elsewhere.
  2. If your workspace requires MFA, you'll be prompted to scan a QR code with your authenticator app and enter the six-digit code it generates. Save your recovery codes somewhere safe, they're the only way back in if you lose your phone.
  3. You'll land on the Fleet overview, which will be empty. That's expected, we'll fix that in a few steps.
caution

Three failed sign-in attempts will lock your account. If that happens, contact ioX-Connect support to unlock it. We don't recommend disabling MFA once it's set up.

Step 2: Brand your workspace​

Before you invite users or onboard customers, set up your branding so the platform looks like your product, not ours.

  1. Open Administration → White Label from the sidebar and stay on the Branding tab. (If you don't see White Label in the menu, it isn't included in your plan; contact ioX-Connect support.)
  2. Set the App name. It's used throughout the UI in place of the default.
  3. Upload your assets:
    • Menu logo, which appears in the sidebar. A landscape mark works best (around 240x64). SVG or PNG, transparent background recommended.
    • Login logo, shown above the form on the sign-in page. This box is larger and squarer, so a logo sized around 280x160 reads best. If you leave it empty, the menu logo is used here too.
    • Favicon, the icon shown in the browser tab.
    • App icon, the icon shown when a user saves your portal to their phone home screen. Square PNG, 512x512 recommended, with a little padding around the mark so rounded corners don't clip it. Without one, phones show a plain letter tile. Users who saved a bookmark before you uploaded an icon need to remove and re-add it to pick up the new icon.
    • Login background (optional), a full-bleed image behind the sign-in page.
    • Powered by logo (optional), under Portal options. Used for the small "Powered by" mark at the bottom-right of dashboards your customers share by public link. It is separate from the menu logo, so you can use a more compact mark, and you can point it at your own site. Uploads and removals take effect immediately; they do not wait for Save.
  4. Set your brand colors (primary, accent, and optionally the left menu background). The interface will tone-map them automatically for dark mode.
  5. Click Save at the top of the tab. Everything on the Branding tab saves together. If you switch tabs with unsaved edits, you are asked whether to keep or discard them.
  6. On the Email tab, set your Support email: the "Need help?" address in the footer of every email sent on your behalf, and where replies to those emails go. See Email deliverability.
  7. (Optional) Add a custom domain on the Domain tab, so your workspace lives at e.g. portal.yourcompany.com instead of the default URL. It's self-service; the Custom domain guide walks through the DNS records and activation.
  8. (Optional) Send emails from your own domain on the Email tab so the sender line carries your brand too. See Email deliverability.
note

Branding is workspace-wide. Sub-accounts inherit your branding by default, so your customers see your brand and not ours.

Step 3: Create your first sub-account​

A sub-account is a tenant inside your workspace, typically one per customer, site, or project. Devices, dashboards, and users live inside sub-accounts.

  1. Open Administration → Sub-accounts.
  2. Click Create sub-account.
  3. Give it a name (you can rename it later) and pick a sub-account tier. The tier controls which features and quotas the sub-account gets; see Setting up sub-account tiers.
  4. Click Create.

Your new sub-account appears in the list. Use the Switch to button on its row to scope into it and see the platform the way that customer will. While scoped in, a banner across the top of the page shows which sub-account you are acting as; click Return to partner view on the banner (or in the user menu, top right) to come back.

tip

If you're just exploring, create a sub-account called Test Lab and use it for everything in this guide. You can delete it later without affecting your real customers.

Step 4: Register your first device​

Devices start life in Inventory, registered to your workspace but not yet active.

  1. Open Administration → Inventory from the sidebar.
  2. Click Register device.
  3. Enter:
    • DevEUI, the 16 hex characters from the device label.
    • AppKey, the 32 hex characters from the device manufacturer.
    • Device profile, the profile that matches your device type. If you don't see one, you can create it yourself (Device Profiles) or contact ioX-Connect support for help.
    • Frequency, the regional frequency plan the device is configured for.
    • Name, a friendly name so you can find it later.
  4. Optionally add a serial number, device type, and description.
  5. Click Register.

The device now sits in inventory, waiting to be assigned. See the Devices guide for the full reference.

note

If your plan includes cellular devices, a Connectivity choice (LoRaWAN, NB-IoT, or LTE-M) appears at the top of the form. Cellular devices register with an IMEI instead of a DevEUI and AppKey. Plans with Blues Notehub add a Blues Notehub option (also IMEI-based); see Blues Notehub.

Step 5: Assign the device to a sub-account​

Assigning a device makes it live on the network and ready to send data.

  1. From Inventory, find the device you just registered.
  2. Open its row menu and click Assign.
  3. Pick the sub-account you created in Step 3.
  4. Click Assign.

Provisioning on the underlying network happens automatically and usually completes right away. If anything goes wrong, the assign dialog tells you; see Troubleshooting.

Step 6: Confirm data is flowing​

Now turn on the device (or wait for its next scheduled transmission).

  1. Open Fleet, switch to the Device List tab, and click your device.
  2. Open the Events tab.
  3. Within a few minutes you should see uplinks arriving, with decoded values from your device profile.

Not seeing anything?

  • Check the device is powered and within range of a gateway.
  • On the device's Configuration tab, confirm the assigned profile matches the device model.
  • If uplinks arrive but the values fail to decode, the profile doesn't match the device. Switch it on the Configuration tab.
  • Still stuck? See Troubleshooting.

Step 7: Build your first dashboard​

Dashboards turn raw telemetry into something useful.

  1. Open Dashboards from the sidebar.
  2. Click New dashboard and give it a name. The dashboard is created in the workspace you're currently viewing, so switch into your sub-account first if it should live there; dashboards created at partner level can bind to any device in your workspace.
  3. Turn on the Edit toggle (top right) and click Add widget.
  4. Pick a type that matches your device's data: a Value widget for a single reading, a Chart widget for trends, a Gauge for ranges, or a Status widget for booleans.
  5. Bind the widget to your device and pick the field to display.
  6. Turn the Edit toggle off to save the layout.

See the Dashboards guide for the full widget library.

What's next​

You've now done the loop end to end: device, sub-account, live data, visualization. From here, common next steps are:

  • Invite your team, adding members to your workspace with the right roles (Administration → Account Settings → Members).
  • Set up workflows, getting notified when a reading crosses a threshold or a device goes offline.
  • Connect more devices, including bulk registration, device profiles, and calibration.
  • Manage sub-accounts, onboarding customers and controlling what each one sees.

Got stuck? Email support@eamstechnologies.com or browse the troubleshooting guide.