Productivity & Workflows
Document360 Review: Separate an Internal Knowledge Base from Customer Documentation
Document360 supports distinct public, private and mixed documentation needs. This review uses a complete publication map and editorial-language matrix to separate readers, authors and publishers and define a comparable custom quote.
Document360 is worth evaluating when customer documentation and internal knowledge need deliberate publishing, ownership and access boundaries. Start by deciding who may read each article, who may edit it and who may publish it. A new category, a different language or an internal-sounding title does not establish that boundary. Its documentation describes separate projects and Mixed access; choose the structure your team can maintain and verify.
This LandOffer.ai review checks official sources on October 27, 2026. Its publication map, staffing matrix and review decisions are original fictional materials. No Document360 project, account, reader, role, access mode, article, translation or domain was created or changed. The example is a completed editorial design, not a security test, migration result or observed publishing workflow. Local checks verify its counts and intended routing only.

Choose the reader boundary before the navigation
Document360's Reader access guide distinguishes Public, Private and Mixed modes. Public permits reading without login; Private requires an account and login; Mixed combines public material with restricted content. These modes concern the reader-facing site, not merely whether a writer can open the editing portal.
The dedicated Public access documentation says published content across the project's workspaces and languages is available to everyone. Reader groups and reader-access inheritance controls do not apply to a wholly Public project. An “Internal” category inside that project is therefore not an internal knowledge base just because its navigation label says so.
Mixed access supports public and private sections, with workspace or language visibility configured independently and reader controls applying to private content. It is a legitimate alternative to separate projects. It also introduces a configuration surface that needs review: confirm the actual access mode and intended audience of every included section before treating the combined site as separated.
The structure guide distinguishes projects, workspaces, languages, categories and articles. Projects are independent documentation sites; workspaces can separate products, versions or audiences; languages provide localized forms of a workspace. This is useful organizational structure, but the reader-access configuration still determines who may read published material.
Ask for a quote against a completed configuration
The current pricing page uses custom pricing rather than a public flat subscription amount. Its FAQ identifies team accounts, workspaces, languages, security requirements, privacy model and AI Premium Suite usage as quote inputs. It also describes revision history, reusable content, review reminders and approval workflows. A feature's presence on that page does not establish an unlimited entitlement in every proposed contract.
Prepare the actual configuration before comparing quotes. An editor or reviewer is a portal user requirement; an employee who only reads private guidance is a different requirement. Keeping those counts separate prevents a read-only audience from being mistaken for the editorial team. Anonymous customers reading a public help center are another audience. Do not add these counts into one unlabeled “users” total and assume the quote will interpret it correctly.
The worked case requests two project options: one combined Mixed project, and a separate public help project plus private operations project. No price is assigned to either. Request comparable language, user, reader and security scope in both offers, along with implementation, support, renewal and excess-usage terms. Without those terms, this review cannot declare that consolidation or project separation is cheaper.
Complete the internal and external publication map
PineShelf is an invented digital-asset product. Leena leads its documentation. Customer help explains how to replace a collection cover; internal guidance explains how support handles repeated cover-processing failures. These are fictional product specifications, not instructions verified against an application. The assumed editorial device is a Windows 11 laptop using Chrome; reader-device behavior remains untested.
Leena chooses separate projects for this design because customer releases and internal operations have different owners and audiences. The proposal does not claim that Document360 requires two projects or that separate projects automatically prevent every exposure. Mixed access remains a comparison option in the quote request.
The proposed Help project is Public. It has Current and Legacy workspaces: Current needs English and French, while Legacy needs English only. The proposed Operations project is Private, with one Operations workspace in English. That is three workspaces and four workspace-language combinations across two projects. The combinations describe documentation coverage, not a claim about how the vendor bills language allowances.
| Content record | Intended destination and audience | Completed editorial decision |
|---|---|---|
| H101: Replace a collection cover, current English | Help / Current / English; public customers after approved publication | Keep only user-facing actions and outcomes. Remove the internal failure threshold and escalation roster from the source packet. |
| H101-FR: Localized cover procedure | Help / Current / French; public customers only after separate language review | Hold the draft after a meaning error is found. Correct the save-versus-publish distinction and request another language review before release. |
| H080: Cover procedure for the legacy interface | Help / Legacy / English; customers using that documented version | Keep the version identification explicit. Do not silently substitute old controls into the current article. |
| I201: Repeated processing-failure triage | Operations / Operations / English; eighteen authorized support readers | Retain the internal routing threshold and staff escalation responsibilities here. Specify restricted content access within the private project. |
| I202: General handoff checklist | Operations / Operations / English; all forty-two intended employee readers | Keep the ordinary handoff checklist separate from the narrower support-only procedure. Private login alone is not the full audience specification. |
| S01: Definition of “cover image” | Separate approved public and internal wording | The authored public definition is approved for this case's customer audience. Do not assume a reusable private source will safely propagate into a public destination across project boundaries. |
H101's completed public excerpt is: “Choose an existing image, save the cover, and check the collection preview. Saving the cover does not publish the collection. If the preview remains incorrect, contact support through the published help route with the collection reference.” It contains no internal roster, routing threshold or promise of a resolution time.
I201's authored internal excerpt separately tells support to record the request reference, compare the reported preview with the processing record and route repeated failures to the designated maintainer under the team's procedure. In this authored case, two consecutive failed processing observations trigger that internal review; this is an invented team rule, not a Document360 behavior or public service promise. Publishing a shorter public explanation does not authorize publishing the private investigation notes or attachments alongside it.
Keep readers, reviewers and publishers distinct
The current Add readers guide says readers can access Private or Mixed knowledge-base content without contributing to or managing it. It also distinguishes reader accounts from portal users and says a person cannot simultaneously hold both roles in the intended project model. Use the appropriate user path for someone who must review a draft in the portal instead of assuming a reader account provides authoring or review powers.
Roles and permissions separates a portal role's administrative capabilities from a content role's article-management capabilities. The two need separate review. An administrator who manages identity configuration need not be the person authorized to publish customer documentation.
The default content-role guide describes Draft writer without publishing rights and Reviewer for inline comments on assigned content. Editor includes publishing capabilities. Its portal-role companion separately describes administrative access. Do not rely on the repeated role name “Reviewer” without checking which role layer and content scope are assigned.
Here is Leena's completed requirements matrix. It specifies intended work, not roles configured in an account:
| Person and project involvement | Required editorial or administrative work | Deliberate exclusion |
|---|---|---|
| Leena — Help and Operations | Own content decisions and carry out authorized publication; evaluate the appropriate content permissions in both projects | Approval of an article does not authorize changing reader-access mode or billing |
| Omar — Help and Operations | Draft and revise assigned material under a suitable non-publishing content role | No independent publication or security administration |
| Jules — Help and Operations | Review technical claims on assigned drafts and record unresolved facts | No assumption that a comment constitutes final publication approval |
| Lucie — Help only | Review French meaning and wording on assigned localized drafts | No Operations access and no publisher role merely because the language review is complete |
| Tariq — Help and Operations | Administer the agreed identity and access configuration with content access limited appropriately | No content editing or publication required by this administrative responsibility |
There are five distinct portal-user candidates and nine proposed project memberships. The quote must explain licensing across projects; nine memberships are not asserted to mean nine billed seats. Forty-two additional employees are reader-only candidates for the private site, divided into eighteen support readers and twenty-four other readers. They are not duplicate reader accounts for the five portal users.
This matrix intentionally defines permissions as requirements rather than handing everyone a broad default role. A real setup needs to inspect the available role combinations, content scopes and contract entitlements. No role grant, invitation or access change is performed in this article.

Complete the language review without publishing the wrong meaning
The workspace guide documents workspace structure, language options and separate workspace statuses. The reader-visibility guide separately documents Public or Private visibility within Mixed projects. Do not treat a workspace status label, language name or hidden navigation option as a substitute for checking reader access.
In the fictional review, Lucie finds that H101-FR tells the reader to publish the collection where H101 only tells them to save its cover. Leena records the defect as a changed action, rather than accepting it as stylistic variation. The corrected authored line is: “Enregistrez la couverture, puis vérifiez l’aperçu de la collection. L’enregistrement de la couverture ne publie pas la collection.” This is an illustrative revision, not a professional certification of the entire translation.
The completed decision record retains H101's reviewed English draft, corrects the French action and keeps H101-FR on hold for a second language check. It also removes an internal maintainer note from the public packet and routes it to I201. No article is actually published. A future release check must establish the real French page, any fallback content, correct links and the actual unauthenticated audience rather than assuming a completed translation task establishes those outcomes.
The same record names maintenance capacity. Omar would reserve forty-five minutes each Tuesday for source-change reconciliation instead of optional layout refinements; Lucie would reserve thirty minutes for French review when a material source action changes. These are proposed allocations, not measured editing durations, accepted calendar events or a guaranteed translation turnaround.
Verify the boundary that you intend to purchase
For this case, the provisional choice is a two-project design with a clearly scoped quote. The customer help project has only approved public material; the private operations project has differentiated employee reader needs. A team comfortable maintaining and verifying granular Mixed access could reasonably choose the combined alternative instead. The cost and administrative difference remain unknown until comparable offers and actual configuration evidence exist.
Before adoption, the authorized owner would need to check a permitted sample from the relevant perspectives: anonymous public reader, general employee reader, restricted support reader, assigned reviewer and publisher. The expected map excludes I201 from the anonymous and general-reader views, while allowing the authorized support view; I202 is intended for both employee groups. Those are acceptance requirements, not tests performed by the local fixture or a claim that access cannot fail.
Also inspect references, media and reused content at the destination. A public article that omits private text can still point to the wrong attachment or internal source. Revision history and review reminders can support maintenance, but a saved version or notification is not proof of correct current permissions, translation or publication approval.
Use the LandOffer.ai workplace-tool library after filling one concrete procurement packet: publication map, project/workspace/language counts, distinct user and reader requirements, publisher responsibilities and unresolved access checks. Keep the current documentation system until the quote names the required configuration and the approved evaluation records the intended reader and publisher outcomes. This review provides the completed design needed to compare options; it does not supply the missing quote or account-side proof.
Sources and Further Reading
- Document360 custom pricing and configuration inputs
- Reader access modes
- Public access behavior
- Mixed access
- Organizing a knowledge base
- Readers versus portal users
- Portal and content roles
- Default content roles
- Default portal roles
- Workspace and language structure
- Workspace and language reader visibility


