how-tos Sign in

How to do things in BE Hub.

Short guides with screenshots of the real console. Written for the person who has just signed in. They follow the console's menu: pick the part you are working in.

Start 4 how-tos

Signing in, the Today page and the first look around.

Sign in to BE Hub
Username and password, or Google / Microsoft if the hub has those turned on.
Read Today
One list of what needs you now, worst first, then the fleet in one line and what happened.
Change the dashboard chart range
Fleet over time is the last day, the last week, or the last month. The highlighted button is the range on screen.
All 4 Start how-tos →

Machines 21 how-tos

The fleet list, finding a machine, and adding new ones.

Install the agent on a machine
One line per platform. It downloads the signed agent, installs the service, and connects.
Hand someone the install page
A page they can open without signing in. The one-liner in the console is a different address.
Install by hand when the one-liner cannot run
Windows and Linux list the same three steps the script would have done.
All 21 Machines how-tos →

A machine 93 how-tos

One machine's page, tab by tab: overview, checks, network, storage, actions and the rest.

Add a disk or ping check
A check is a named test the agent runs on a schedule. Failures become alerts.
Choose how often a check runs, and how serious it is
Interval is 1m to 24h. Severity is info, warn, or crit, and that becomes the alert's severity.
Push checks to the agent
The list on screen is a draft. Push replaces the whole document on the machine, and it asks you to confirm.
All 93 A machine how-tos →

Approvals 11 how-tos

Changes BE AI proposes, and approving, rejecting or retrying them.

Approve or reject a proposal
BE AI files the exact command. A named person approves. The audit trail keeps both.
Retry a proposal that failed
Retry is on a row that never ran. The first press asks you to confirm. The second press runs it again.
Show only failed proposals
The status menu keeps failed, or executed, and hides the rest. Nothing runs.
All 11 Approvals how-tos →

Alerts 59 how-tos

Open alerts, who gets told (rules), what was sent, and scripts that run on an alert.

Work an open alert
Ack, discuss, resolve, or accept a condition that is known and fine.
See resolved alerts on the alerts page
Open + acked hides anything that already cleared. Resolved brings those rows back.
Acknowledge an alert
Ack means a person saw it. The alert stays open. A comment is optional.
All 59 Alerts how-tos →

Patches 17 how-tos

Missing updates, approving them, and jobs that install them.

Review and approve missing updates
Inventory, approve, schedule a job. Approving installs nothing by itself.
See updates from one source
The source menu keeps Windows Update, or winget, and hides the rest. Search matches the title or the KB.
Search the update list
Type a name, a KB, or an id. Rows that do not match drop out. Nothing is approved.
All 17 Patches how-tos →

Security 6 how-tos

The daily security check, fixing findings, and the monthly report.

Read the Security page
A score per company, what is open, and which machines have not been checked.
Accept or reopen a security finding
A finding you have decided to live with stays on record, with your reason, and stops counting against the score.
Work through the security checklist
Every open finding has someone to handle it, a due date, and a record of when it was done.
All 6 Security how-tos →

Scripts 25 how-tos

The script library, running scripts, their runs and onboarding rules.

Run a saved script
A script is text with {{variables}}. Run renders it per machine and sends it as an approved command.
Stop a script that is still running
Scripts › runs. Stop is on a row that is still going. The first press asks you to confirm. The second press stops it.
Show script runs that have finished
The status menu hides runs that are still going, or keeps only those. The runs themselves stay.
All 25 Scripts how-tos →

BE AI 11 how-tos

Discussing a machine or a group with BE AI, and its investigation history.

Ask BE AI about a machine
Discuss is a thread. BE AI looks, then proposes. You approve. It never runs a mutating tool on its own.
Start from a prepared question
The shortcuts under the composer fill the box. They do not send.
Ask BE AI about a group
One conversation for a site, a tag, or everyone in the company. It proposes. You approve.
All 11 BE AI how-tos →

Tickets 2 how-tos

The ticket queue, replying, and raising tickets.

Work the ticket queue
Tickets from email, the portal, alerts and the phone in one queue: unassigned first, then whatever is due soonest.
Reply to a ticket
A public reply goes to the requester by email; an internal note stays with the technicians.

Knowledge base 1 how-to

Articles, company and requester profiles, and BE AI's additions.

Use the knowledge base
Articles, a profile of each company and of each requester. BE AI adds to it when tickets resolve; you review, revert or publish.

Reports 19 how-tos

Report templates, saving them, and the morning brief.

Build a report of the fleet
Saved views of disks, patches, approvals, online — filtered by type, tag or company.
Save a report you will open again
The name keeps the template and the filters. Machines still enter and leave.
Delete a saved report
Delete takes the name off the Reports menu. The first press asks you to confirm. The machines stay.
All 19 Reports how-tos →

Company 27 how-tos

Company settings, sub-companies, remote control and BE AI's schedule.

Watch or take control of a screen
On an online Windows machine: one click. A second window holds the keyboard. Sessions are recorded.
Add a company for a customer
The organisation's owner creates a company. It gets its own install link, alert rules and machines.
Company notes, schedule and remote control
Notes for BE AI, the nightly pass, the install link, and whether Control is on.
All 27 Company how-tos →

Settings 16 how-tos

Your display and account, users, the service desk and AI agents.

Take tickets by email
Each organisation gets a support address. Forward your support mailbox to it and every email becomes a ticket.
Set up ticketing
Switch it on, set business hours and targets per priority, categories, canned replies.
Invite a teammate
A named seat. Email as username sends an invitation; they set their own password.
All 16 Settings how-tos →

Agent updates 2 how-tos

Rolling out a new agent version and the hub address.

Push an agent update
Pick a signed release and who should get it. The agent checks the signature and swaps itself.
See which address a machine connects through
Updates lists the hostname each machine last reported. Re-point moves online machines that are still on an old name.

Usage and billing 2 how-tos

What the organisation uses and pays for.

Read seats and this month's BE AI
People are seats. An investigation that reached the model is a run. Machines are neither.
Read an earlier month
The month menu is UTC. Seats stay as they are today. The investigation tiles follow the month you pick.

Events 2 how-tos

Everything machines and the hub reported.

Read the event stream
Reboots, disk-high, check failed, WAN change, Wi-Fi drop — one line each.
Show only one kind of event
The Events page is the whole company. Pick a kind and the list narrows at once. The other kinds stay stored.

Audit trail 5 how-tos

Who did what, permanently recorded.

Search the audit trail
Who called which tool, who approved, who opened a machine, who was refused.
Show when someone opened a machine
The kind menu keeps one sort of record. Opening a machine stays. Leaving it drops out. Nothing is deleted.
Limit the audit trail to one machine
The machine menu reloads the list for that machine only. Other lines stay stored.
All 5 Audit trail how-tos →

For customers 42 how-tos

What a customer user sees: their computers, approvals and tickets.

See the computers you were given
After you sign in, the strip names your login and the machines in your groups. The rest of the company stays with your provider.
Find one of your machines
The find box matches a name, a hostname, an address, a site, or a tag. Machines outside your groups are not in the list to begin with.
Show only your machines that need attention
The Needs attention tick hides machines that are fine. Clear it to see every computer you were given.
All 42 For customers how-tos →

Not a how-to (on purpose)

Screenshots are of a demo company, not a customer. Open the same screen in your own console and follow along.