Help guide

Castum user guide

Everything you need to enroll Android devices, deploy apps and keep a fleet of kiosks and payment terminals running. Pick a topic, or read it top to bottom.

Español

Getting started

Castum is Android MDM for kiosks and payment terminals. You enroll devices, send them apps, and watch their health from one console.

The short path

Most teams are running in a few minutes.

  • Create your account and start a subscription under Billing.
  • Add a location, then enroll a device by scanning a QR code.
  • Upload your signed APK under Apps.
  • Deploy it to the account, a location or a group.

Start a subscription first

Until a subscription is active you can look around, but enrolling devices and managing the fleet stay paused. A banner at the top of the dashboard links straight to Billing.

Who can do what

Your role decides what you see. Admins manage everything, Users operate devices, and Viewers read only. The Team and roles section explains each one.

Enroll devices

Enrolling connects an Android device to your account. You do it once per device with a short-lived QR code.

Scan the QR code

Open Devices, choose Enroll device, pick the location (and a group if you like), and a QR code appears. Scan it on the device. The page waits and confirms as soon as the device checks in.

The code expires

For safety the QR code is valid for a short time, 15 minutes by default, and works for one device. If it runs out, create a new one. Use Enroll another to add the next device.

Slots

Each enrolled device uses one slot from your subscription. The allowance card at the bottom of the sidebar shows how many you have used. When there are none free, add devices under Billing before enrolling more.

Locations and groups

Organize devices so you can target them together later.

Locations

A location is a physical place, such as a store or a venue. Each device belongs to one location. Add one from the panel on the left of Devices. You can rename a location, and you can delete it once no devices remain there.

Groups

A group cuts across locations, for example all countertop terminals or all self-service kiosks. A device can be in several groups. Use groups to roll an app out to a type of device rather than a place.

Find a device

Search by name or device ID, and filter by connectivity or install status. Select All devices to clear the filters.

Apps and releases

Upload the Android apps your devices run. Castum keeps every version as a release you can deploy again.

Upload a signed APK

Under Apps, upload your APK. Castum reads the package name, version and signing identity from the file itself. Unsigned APKs are refused.

Releases never change

Each upload becomes an immutable release. That means the exact build you tested on a pilot device is the build that reaches production. To ship a fix, upload a new build and deploy it.

Business and companion apps

Apps are tagged as Business (the app your customers use) or Companion (supporting apps). You will see the tag next to each app in the list.

Deploy to devices

Choose a release, choose who gets it, review, then send.

Create a deployment

Go to Deployments, then New deployment. Pick a release and one or more targets: the whole account, a location or a group.

Review before anything is sent

Castum shows the unique devices the deployment will reach, so a device that is in two targets is counted once. Nothing is sent until you confirm.

Which release wins

When targets overlap, the most specific one wins.

  • A release pinned to a single device beats everything.
  • A location or group target beats the account default.
  • The account default applies when nothing else does.
  • If two different releases reach a device through a location and a group, Castum flags a conflict for you to resolve.

Retry failed installs

Open a device to see the status of each app. If an install failed, select it and choose Retry selected installs.

Kiosk profiles

A kiosk profile decides what a device is allowed to show.

Approved app or app list

Create a profile under Apps. A profile can lock the device to a single approved app, or allow a short list of apps. You can also have the app launch when the device boots.

Assign it

Set the profile on a device or group from its edit page. A profile cannot be deleted while a group or device still uses it.

Who can edit

Admins and Users can create and change kiosk profiles. Viewers can see them.

Monitor your devices

See at a glance what is healthy and what needs attention.

The Devices overview

The top of Devices shows enrolled devices against your slots, how many are online or offline, and install failures, including devices still waiting to check in.

Online and offline

Each device checks in regularly. If a device stops checking in for a while, 10 minutes by default, it shows as offline.

A single device

Open any device to see its model, Android version, agent version, when it enrolled and last checked in, its groups, kiosk profile, installed apps and recent events.

Incidents and logs

Castum turns noisy device events into a short list of things to act on.

Incidents

Related events are grouped into one incident, so a store going dark is one item and not fifty. Castum raises incidents for missed check-ins (an outage or a partial outage) and for repeated install failures. An incident closes by itself when things recover.

Logs

Logs hold the detailed events for your account. They are redacted and scoped to your account. Routine check-ins are not listed here, they live in each device's health history.

Notifications

Notifications are handled by Roomwork, so incidents reach your team where they already work.

Connect Roomwork

Admins open Notifications and choose Connect to Roomwork, then pick which rooms Castum may use. We suggest a dedicated Roomwork account, such as an alerts user, so incident posts do not appear under one person's name.

Messages and tasks

Choose a room for messages and a project for tasks. Castum posts each incident to the room with its severity, scope, incident ID and a link back to Castum, and can create one task per open incident.

Control the noise

Decide which incidents create tasks: outages only, outages and critical anomalies, or everything detected. A repeat-alert window (30 minutes by default) stops the same incident from posting again and again. The Routing preview on the page shows exactly what would be sent.

Team and roles

Invite your colleagues and give each one the right level of access.

Admin

Manages members, billing, fleet operations and Notifications settings. Keep this for the people who run the account.

User

Operates the fleet: enroll, group and deploy. Cannot change billing or members.

Viewer

Read-only access to devices, logs and incidents. A good fit for support and stakeholders.

Invite and switch accounts

Admins invite people from Members. If you belong to more than one customer account, the account picker at the top of the sidebar switches between them.

Billing

Simple per-device pricing, billed in small batches.

How you are billed

Billing is per device and is sold in batches of five. Choose monthly or annual billing. Admins manage the subscription under Billing, and change the number of devices there so your allowance always matches what you pay for. See the Pricing page for current rates.

Cancel your subscription

Admins can choose Cancel subscription on the Billing page. It opens a short message to the Castum team, and we confirm the cancellation with you by email.

If a payment fails

You get a 7 day grace period to fix it. If the subscription lapses, enrolled kiosks keep running the apps already installed, but enrolling and managing devices is paused until it is renewed.

Retiring a device

Retire a device from its page when you no longer need it. This frees its slot and removes its access to management commands. Apps already installed keep running. Retiring cannot be undone.

Troubleshooting

The most common questions, with the quickest fix.

My device never appeared after scanning

The QR code probably expired, or the device could not reach the internet. Create a new code, make sure the device is online, and scan again. Also check that you have a free slot.

A device shows offline

Check power and network on the device first. Once it can reach the internet it will check in again and return to online on its own. A whole location going offline raises one incident.

An install failed

Open the device, select the failed app and choose Retry selected installs. If it keeps failing, the Incidents page groups repeated failures so you can see the pattern, and Logs has the detail.

I cannot see Billing or Members

Those pages are for Admins. Ask an account Admin to change your role if you need them.

Still stuck?

Write to the Castum team and we will reply within one business day.

Contact us