Skip to content
docs

Type at least two characters. Press Enter for full results.

    Plan feature reference

    View as MarkdownOpen in ChatGPTOpen in Claude

    This page lists every feature that depends on your Outpost plan, which plans include it, and exactly what you see when your plan does not: in the console, on the endpoint, and from the API. It is for technicians who meet a refusal and developers who need to handle one. For what each plan includes and costs, see Plans and limits.

    Scope

    Section titled “Scope”
    • Depot 0.8.0.
    • Features every plan includes, such as endpoint management, remote desktop over direct connections, scripting, patching, backup, documentation, security framework baselines, and the audit log, are not listed. See Features by plan.
    • Numeric limits on endpoints, unmanaged devices, and console users are on Plans and limits.
    • What the console looks like when a feature is locked, and how owners hide locked features, is on Plan-locked features.

    Features

    Section titled “Features”
    FeaturePlansWithout it, in the consoleAPI refusal
    Service deskEnterprise, MSPTickets, incidents, status pages, SLAs, and the ticket list in the inbox are locked. The tray app does not offer live chat.402, reason plan_feature, limit feature:service_desk
    PSAMSPSales, projects, and client billing are locked.402, reason plan_feature, limit feature:psa
    Multiple client environmentsMSPAdding a second client is refused with Plan limit reached.402, reason plan_limit, limit clients
    Relayed remote desktopEnterprise, MSPRemote sessions use direct connections only.None. The session is set up without a relay.
    Session recordingEnterprise, MSPRecording is hidden in the profile editor. Profiles that require recording cannot be applied.402, reason plan_feature, limit feature:session_recording, when applying one
    Roles and permissionsEssentials, Enterprise, MSPGranting or removing a role is refused with Plan limit reached.402, reason plan_limit, limit roles
    Outpost Cloud StorageEssentials, Enterprise, MSPStoring a file is refused with Add your own storage until you add your own S3-compatible storage.402, reason own_storage_required, limit storage

    Every 402 has the body described in For API clients. Its detail is the sentence the console shows.

    Notes on individual features

    Section titled “Notes on individual features”

    Service desk

    Section titled “Service desk”

    The console names this feature Service desk. Without it:

    • Tickets, Incidents, Estate status, the ticket list in Inbox, and Settings > SLA are locked in the navigation. An owner sees them with a lock and a page that says which plan includes them. Everyone else does not see them.
    • The API refuses ticket, ticket configuration, satisfaction survey, ticket automation, SLA, knowledge base, incident, maintenance window, and status page configuration requests with Not included in your plan.
    • A help request sent from the tray app does not open a ticket. See Use the Outpost tray app.
    • Live chat is not offered. People cannot start a chat from the tray app or see their past chats there, and Raise a ticket on a chat is refused. A chat already running when the plan changes can finish. See Live chat.
    • Your public status page and satisfaction survey links answer 404 Not Found, the same as an address that never existed.

    PSA

    Section titled “PSA”

    The console names this feature PSA. It covers Sales, Projects, and Client billing, which exist only in an MSP console. In any other console these sections do not appear, and their API routes answer 404 Not Found. On an MSP console without the feature:

    • The three sections are locked in the navigation, the same way as the service desk.
    • The API refuses sales, project, and client billing requests with Not included in your plan.
    • Quote acceptance links and project status links sent to your customers answer 404 Not Found.

    Multiple client environments

    Section titled “Multiple client environments”

    Without it, your Outpost holds one client. Creating another is refused with Plan limit reached and a message that names your plan and says it “includes one client environment”. Clients that already exist are not removed. See Add and manage clients.

    Relayed remote desktop

    Section titled “Relayed remote desktop”

    Without it, remote desktop sessions use direct connections only, and no relay credentials are issued for them. Where your Outpost connects remote sessions only through a relay, the session is refused with “Relayed remote desktop is not included in your plan.” See Remote access.

    Session recording

    Section titled “Session recording”

    Without it:

    • remote_access.recording_required is hidden in the profile editor.
    • Saving or assigning a profile that requires recording is refused with Not included in your plan, and so is restoring or rolling out a saved profile version that requires it.
    • A profile that already required recording before the plan changed keeps working. Its sessions run unrecorded, the profile shows This profile requires session recording, but your plan does not include it. Remote sessions run unrecorded., and the viewer shows Policy requires session recording, which is not included in this plan. This session is not being recorded. Each such session is recorded in the audit log.

    Recordings made earlier stay listed and playable. See Record remote sessions.

    Roles and permissions

    Section titled “Roles and permissions”

    On Home Lab, the one console user is the owner, and requests to grant or remove a role are refused with “Home Lab has one console user, who is the owner. Upgrade to Essentials to use roles.” See Roles and permissions.

    Outpost Cloud Storage

    Section titled “Outpost Cloud Storage”

    Home Lab stores files only in your own S3-compatible storage. Until you add it, anything that would store a file in Outpost Cloud Storage is refused with “Home Lab uses your own S3-compatible storage. Add your own S3-compatible storage to store files.” Files already stored stay readable. See Storage destinations.

    How your plan is checked

    Section titled “How your plan is checked”

    Your Outpost asks the Outpost service which plan you are on and keeps the answer for 15 minutes before asking again, so a plan change can take up to that long to unlock or lock a feature.

    If your Outpost cannot reach the Outpost service, it keeps using the last plan it verified, for up to 72 hours. After that, until the connection returns, it treats your plan as unverified. The features on this page are refused, and so are enrolling more endpoints, tracking more unmanaged devices, adding console users, and storing files in Outpost Cloud Storage. Some of these refusals read Plan verification unavailable (503, reason plan_unavailable). Endpoints already enrolled, and features every plan includes, keep working. Once your Outpost reaches the Outpost service again, the next check restores your plan.

    Self-hosted deployments and Remote Outpost check their plan differently. See Self-hosted and air-gapped deployments.

    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.