Concepts and vocabulary
This page defines the words the rest of this documentation uses without stopping to explain them. Read it once before you set up Outpost, and come back when a term on another page is unclear. The console uses the same words.
Where you work
Section titled “Where you work”The console
Section titled “The console”The console is the web application your team signs in to at your Outpost address. It is where you manage endpoints, run scripts, connect remotely, and work tickets. Everyone on your team signs in to the console with their own account. See Console.
The Outpost portal
Section titled “The Outpost portal”The Outpost portal is where the account owner signs up, chooses and changes the plan, and manages payment methods and invoices. It is separate from the console. Most technicians never need it. See Account and billing.
Your Outpost address
Section titled “Your Outpost address”Your Outpost address is the web address of your console, a name you choose at
signup under outpostplatform.com. You and your team sign in there, and your
endpoints report there. The address cannot be changed after signup. See
How Outpost is hosted.
What you manage
Section titled “What you manage”Endpoint
Section titled “Endpoint”An endpoint is a computer with the Outpost agent installed. The console calls them endpoints, and so does this documentation. See Endpoints.
Unmanaged device
Section titled “Unmanaged device”An unmanaged device is a device Outpost tracks without an agent, such as a switch, printer, camera, or access point that network discovery finds. A device that discovery finds counts toward your plan only when you choose to track it.
Active endpoint
Section titled “Active endpoint”An active endpoint is an endpoint that is online for four hours or more in a billing period. The hours do not have to be continuous. Enterprise and MSP bill for active endpoints, so an endpoint that stays offline for a whole period costs nothing for that period. See What counts as an active endpoint.
Enrollment
Section titled “Enrollment”Enrollment connects an endpoint to your Outpost. You download an installer from the console and run it on the computer. The installer carries the details the agent needs to reach your Outpost and to join the right client and site, so the endpoint appears in the console without further setup. See Install and enroll the agent.
Retire
Section titled “Retire”Retiring an endpoint removes it from management. The console action is Retire endpoint. A retired endpoint stays in the console with the status Retired, so its history is kept.
How endpoints are organized
Section titled “How endpoints are organized”Client
Section titled “Client”A client is one organization whose endpoints you manage. On the MSP plan, each organization you serve is a separate client with its own data. On Home Lab, Essentials, and Enterprise, there is one client: your own organization. See MSP.
A site is a physical location that groups endpoints, such as an office or a data center. The console lists sites under Endpoints > Sites.
Device group
Section titled “Device group”A device group is a named group of endpoints by function, such as front desk computers or build servers. The console lists them under Endpoints > Device groups.
A tag is a label a technician applies to endpoints to find and target them. The console lists tags under Endpoints > Tags.
How endpoints are configured
Section titled “How endpoints are configured”Profile
Section titled “Profile”A profile is a named bundle of settings, such as a patch schedule, firewall settings, or a password policy. You assign a profile to your whole organization, a site, a device group, or one endpoint, and some settings to users and user groups. See Automation.
Policy
Section titled “Policy”Policy is the set of settings an endpoint ends up with after every profile that applies to it is resolved. The console shows it under Profiles > Effective config.
Baseline
Section titled “Baseline”A baseline is a built-in profile that implements a compliance framework. When you choose a framework, its baseline is assigned to your whole organization and decides which settings your own profiles are not allowed to weaken. See Compliance.
Who is involved
Section titled “Who is involved”Technician
Section titled “Technician”A technician is anyone on your team who signs in to the console. What a technician can see and do depends on their role.
The owner is the console role with full control, including billing and the plan. The person who signs up is the first owner, and you can invite more.
End user
Section titled “End user”An end user is the person who uses an endpoint day to day. End users do not sign in to the console. They use the Outpost tray app on their computer, which shows its status and gives them a way to reach your support team. See Tray.
Related
Section titled “Related”Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either license.