Get Endpoint Control
Endpoint Control puts the Huntbase endpoint agent on your hosts, so you can ask them questions directly, collect files from them and act on them. It is set up once per organisation. You ask for it from Endpoints: choose your agent address, send the request and follow it on the same page. When your fleet is ready, you go straight to Deploy to install the endpoint agent.
You don't create a connection or enter any server details yourself. Huntbase sets up the fleet and connects it for you.
Before you start
- Work in an organisation. Endpoint Control is set up for organisations, not for your personal workspace. If you are in your personal workspace, the card says Endpoint Control is set up for organisations. Switch to an organisation with the Scope selector first.
- Check your plan. If your plan doesn't include Endpoint Control, the card shows a plan notice in place of the request form, with See plans for org admins. If your plan includes it, the card says so: "Your plan includes it. It's set up per organisation: request it here and we'll create your fleet."
- Browse the sample fleet while you wait. If your organisation has sample data, the read-only Example Corp sample fleet stays open in Endpoints the whole time.
Open the setup page
Any of these opens Set up Endpoint Control:
| Where | What you click |
|---|---|
| Endpoints, when your organisation has no fleet of its own | The setup card fills the Overview tab. |
| Endpoints, while you browse the sample fleet | Set up Endpoint Control on the banner at the top. |
| Endpoints › Deploy | Set up Endpoint Control. |
| Connections | The Endpoint Control card. See Endpoint Control. |
| Onboarding, on the Get data in step | Manage your own endpoints? |
| The Home checklist | Set up Endpoint Control. |
Choose your agent address
Your agent address is what your endpoint agents connect to, for example acme.ec.huntbase.io. Pick a name your team will recognise. You type only the first part; the rest of the address is shown next to the box.
The box starts with a name based on your organisation's name. Keep it or type your own. As you type, Huntbase checks the address and shows the result under the box:
| Message | What it means |
|---|---|
| … is available | You can request this address. |
| Checking … | The check is still running. |
| … is taken. Try another name. | Another organisation already uses it. |
| "…" is reserved. Try another name. | The name is kept for Huntbase's own use. |
| Use lower-case letters, numbers and hyphens, starting and ending with a letter or number. | The name breaks the rules below. |
| Couldn't check that address. You can still send the request. | The check didn't respond. You can send the request, and the team checks the address when it sets up your fleet. |
The rules for the name:
- Lower-case letters (
a–z), digits (0–9) and hyphens only. Capitals are made lower-case, and spaces, dots and underscores become hyphens as you type. - It must start and end with a letter or a digit.
- Up to 40 characters.
- Some names are reserved, such as
www,api,admin,mail,docsandsupport. Addresses already used by another fleet are also unavailable.
Where custom agent addresses aren't offered, the card shows no picker and says "We'll assign your agent address when we set up your fleet."
Send the request
- Under Anything we should know?, add an optional note, such as how many hosts you have, which platforms and your timelines.
- Click Request access.
The card changes to Endpoint Control requested. If the request couldn't be sent, Couldn't send it — email us instead opens a pre-filled email to the Huntbase team.
Your organisation can have only one open request for Endpoint Control. If someone in your organisation has already asked, you see that request rather than a second one.
Follow your request
The card always shows where your request stands. Every member of the organisation sees the same card.
| Status | What you see | What happens next |
|---|---|---|
| Requested | Endpoint Control requested, with the date, who asked, the reference (AR-…), the agent address and your note. | The Huntbase team reviews the request. On some plans it may be approved straight away. You can cancel it. |
| Setting up | Setting up your fleet, with the agent address and a short list of steps that tick off as they finish: Create your fleet, Set up your agent address, Check agents can reach it. | This usually takes a few minutes. You can leave the page; you'll be notified when it's done. |
| Ready | Your fleet is ready at … and Install the endpoint agent. | Click Install the endpoint agent to open Deploy for your new fleet. See Install on endpoints. |
| Declined | We couldn't enable Endpoint Control last time, with the team's note when there is one. | Change what the note asks for, then click Request again. |
If setup runs into a problem, the card says Setup hit a problem; the team has been told, with the reference and the step that failed. There is nothing for you to do: the team fixes it and contacts you.
While your organisation has no fleet of its own, a banner at the top of the sample fleet shows the same status, for example Approved — setting up your fleet. This usually takes a few minutes., with View progress.
How long it takes
Requests are reviewed by the Huntbase team, so approval isn't instant unless your plan approves it straight away. Once a request is approved, setup usually takes a few minutes. When the fleet is ready, it is already connected under Connections as Endpoint Control. The person who asked is an admin of that connection, so they can see the install commands straight away.
Notifications
The person who asked and the organisation's admins are notified at each step. Notifications appear in the bell and, by default, by email. They sit in the Account and organisation category of your notification preferences.
| Notification | What it says |
|---|---|
| Endpoint Control request approved | "Your Endpoint Control request was approved. We're setting up your fleet now." |
| Your Endpoint Control fleet is ready | "Your fleet is ready. Endpoint agents connect to … Open Endpoints to get the install command." Its action opens Deploy. |
| Endpoint Control request declined | "Your Endpoint Control request was declined.", with the team's note. |
| Endpoint Control setup hit a problem | "We couldn't finish setting up your Endpoint Control fleet. Our team has been told and will be in touch." |
When the team adds a note, it appears at the end as "Note from the Huntbase team: …".
Cancel a request
While a request is Requested, click Cancel request on the card. The person who asked and the organisation's admins can cancel. A request that is already setting up can't be cancelled.
Next steps
- Endpoint Control — install the endpoint agent and manage the install link
- Endpoints overview — fleets, scope and the workspace tabs
- All devices — see which hosts don't have the endpoint agent yet