Antylogic
DemoApp login

399 operational guides

Docs sections
DocsDocumentation
Device

Open a Public Docs Article

Open a direct public Docs link, let the landing Docs screen resolve the article through the public index, and read the rendered guide without signing in or changing Harbor Demo Group or Harbor Soho data.

In this article

Use this guide when an operator, support teammate, or documentation reviewer needs to confirm that a public Docs article opens from a direct GB English URL.

Reading the public article is separate from the operational action described inside it. Permissions such as `users:manage` belong to creating an internal user, not to viewing this help page.

Before you start

  • Use `/docs/access/en-access-users-create-location-internal?lang=en-GB`.
  • The public landing site and public Docs API are reachable from the browser.
  • The English article exists in the bundled Docs content; `lang=en-GB` normalises to Docs locale `en`.
  • Published media is optional for this article. Planned media without a resolved source appears as a placeholder.

Instructions

  1. 1.

    Open the public article link

    Open `/docs/access/en-access-users-create-location-internal?lang=en-GB`. The landing Docs article screen should open directly with no sign-in, organisation selection, or Harbor Soho membership check.

  2. 2.

    Confirm the resolved article

    After the public index loads, confirm the selected article is in the Access section and titled `Create an Internal Location User`. The page matches the route by section slug `access` and article slug `en-access-users-create-location-internal`.

  3. 3.

    Read the rendered guide

    Use the article header, summary, intro, prerequisites, ordered steps, validations, expected result, related same-section guides, and right-side anchors. Treat any product permissions mentioned in the article as requirements for the documented product action, not for reading the public page.

  4. 4.

    Change the device view when needed

    Use the Docs device selector only when you need content or media planned for another device. Changing the selector reloads the public index and the selected article with the new platform.

  5. 5.

    Handle loading problems

    If the article area shows an error, check the public API origin and the exact section and article slug. Do not use `HEAD /api/public/docs/{path}` to prove a specific article exists, because the handler can return OK before article lookup.

Validations and limits

  • The public page resolves `lang=en-GB` to Docs locale `en`.
  • The index request is `GET /api/public/docs?locale=en&platform={platform}&theme={theme}`.
  • The detail request is `GET /api/public/docs/access/en-access-users-create-location-internal?locale=en&platform={platform}&theme={theme}` and does not send sidebar search text as `q`.
  • No authenticated user, organisation membership, location membership, or operational permission is required to read the public article.
  • The frontend sends only `mobile`, `tablet`, or `web`; the backend normalises supported platform and theme values.
  • A missing direct article match skips the detail request in the UI; a direct backend GET for an unknown article returns `404`.
  • Planned media without a resolved `src` does not block article rendering; it appears as a pending media placeholder.

Expected result

The public Docs article is readable from the GB route and can be verified against the public detail JSON contract without creating users, assigning roles, opening support requests, or mutating product data.

Related articles