{"id":3348,"date":"2026-10-26T20:00:00","date_gmt":"2026-10-26T12:00:00","guid":{"rendered":"https:\/\/www.olares.com\/articles\/?p=3348"},"modified":"2026-10-27T14:50:26","modified_gmt":"2026-10-27T06:50:26","slug":"keep-client-files-separate-knowledge-base","status":"publish","type":"post","link":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/","title":{"rendered":"How to Keep Client Files Separate From a Personal Knowledge Base"},"content":{"rendered":"

Keep client files separate by sorting everything into three groups: client records, engagement working notes, and your own independent research. By default, only the third group belongs in a personal knowledge base. A client-derived insight should join it only after the engagement terms allow that reuse.<\/p>\n

Each group should live behind a boundary your tools actually enforce. A folder name or a promise to be careful does not decide who can open a file or what a search returns. Good client file separation means access, search, sharing, and deletion all stop at the client line.<\/p>\n

Separate the material by what it is and who owns it<\/h2>\n

Sort material by where it came from and which engagement it serves. File type doesn’t decide this, and neither does whether a document shows names.<\/p>\n

Client records<\/strong> include anything the client gave you, the deliverables you produced for them, and any note that exposes facts specific to the engagement. These stay in a client-specific record, one per client.<\/p>\n

Engagement working notes<\/strong> are your drafts, meeting notes, analysis, and inferences about one client’s situation. They are your own writing, but they are built on client information. Keep them with that engagement. Don’t file them in a reusable personal library just because you wrote them.<\/p>\n

Personal research<\/strong> is material you gathered on your own, from sources that have nothing to do with a client relationship. This is what a personal knowledge base is for.<\/p>\n

Here is an illustrative example. A consultant on a retail pricing project receives the client’s sales export. That export is a client record. She writes a memo on why the client’s discount schedule erodes margin, which makes it an engagement note. She also saves a published industry report she found on her own, and that is personal research. The memo still counts as client-bound even if she deletes the client’s name, because its substance came from the client’s data.<\/p>\n

If a client record contains personal data, the case for physical separation gets stronger. NIST recommends keeping personal data in a different repository<\/a> when practicable. That recommendation covers personal data specifically. For other client files, the three-group model is a practical way to organize, not a legal classification.<\/p>\n

Choose a workspace or collection by the boundary it enforces<\/h2>\n

Use a separate workspace or repository<\/a> when client material needs different access or handling rules than your personal knowledge. A collection inside one shared tool is enough only when its actual controls draw the same line a separate workspace would.<\/p>\n

A label like “Client A” changes nothing about who can see the files or what the tool indexes<\/a>. Before you trust a collection, confirm four behaviors in the tool’s documentation or settings:<\/p>\n

    \n
  1. Access:<\/strong> Can you limit a collection to specific people<\/a>, so a collaborator on one engagement can’t open another client’s files?<\/li>\n
  2. Search and retrieval:<\/strong> Does search, indexing, or a built-in assistant stay inside the collection, or can it pull client content into results while you work on personal research?<\/li>\n
  3. Sharing:<\/strong> When you share a note or a link, does the share stay inside that collection’s permissions?<\/li>\n
  4. Retention and deletion:<\/strong> Can you keep or delete one client’s material on its own schedule without touching your personal library?<\/li>\n<\/ol>\n

    If any answer is no, or the tool doesn’t document it, treat the collection as unconfirmed. A separate workspace is only a valid alternative if you verify those same access, retrieval, sharing, and retention controls for it as well; if your tool cannot confirm those boundaries for either setup, it does not offer a verified option for separating that client’s files.<\/p>\n

    Who uses the system changes which checks matter most. A solo consultant may be the only person with access, but cross-collection search and accidental sharing still apply. In a small practice, engagements can have different authorized collaborators. Workspace membership then becomes the key control. One shared workspace for everyone tends to blur who may see or reuse which client’s material.<\/p>\n

    Two official sources help set the target, within their stated scope. NIST’s personal-data guidance<\/a> recommends role-based access controls, meaning permissions follow a person’s role instead of being granted file by file. Whether your tool can do this at the workspace or collection level is something to confirm in that tool. When client records include sensitive consumer personal information, FTC business guidance advises limiting access to employees with a legitimate business need<\/a>. The same guide recommends keeping that data only while a business reason exists. If you must keep it, it advises a written retention policy covering what you keep, how you secure it, how long you keep it, and how you dispose of it. A storage setup that can’t delete one client’s data separately makes that policy hard to follow.<\/p>\n

    Use a permission-and-purpose gate before reusing client-derived insights<\/h2>\n

    A general lesson from client work stays client-bound until the engagement terms and any applicable permission support reuse. Run every candidate note through the same short gate before it enters your personal knowledge base.<\/p>\n

    \"A
    A flowchart routes independent research to a personal knowledge base and checks client-derived notes for reuse permission and purpose fit.<\/figcaption><\/figure>\n

    First, trace the origin. If the insight came from sources you gathered independently, it already belongs in personal research. If it came from client-provided material or engagement-specific facts, it is client-derived and the gate applies.<\/p>\n

    Next, check the engagement terms. Look at what the contract, statement of work, or confidentiality terms say about work product and reuse. Also check any written permission the client has given. If the terms allow it, the note can move. If they forbid it or say nothing clear, keep the note in the client context and ask the client before moving anything.<\/p>\n

    Removing names, figures, or other identifiers does not establish permission to reuse material. De-identification changes how a note looks, but it does not determine whether applicable contracts, licenses, or confidentiality obligations permit reuse.<\/p>\n

    When the insight involves personal data, add a purpose check. NIST advises<\/a> considering predictability and manageability before deciding whether data can be used beyond its initially expected and agreed purpose. In practice, ask two questions. Would the people the data describes reasonably expect this new use? Could you still manage and control the data once it sits in your personal library? This is a consideration for personal data, not a full legal test, and it doesn’t settle a client’s contractual rights.<\/p>\n

    The gate has only two outcomes. Move the note when reuse is permitted and the new use fits the approved purpose. Otherwise, it stays in the client record. When a note does move, save the basis for the move with it, such as the contract clause or the client’s email. That way you can show later why the note is there.<\/p>\n

    FAQs<\/h2>\n

    Can I keep public research I found during a client engagement?<\/h3>\n

    Do not assume public research can automatically move into your personal library just because you could have found it independently. First check the applicable source licenses and your engagement terms, which may classify materials gathered during the engagement as client work product. When terms and licenses permit keeping the public source, you can save a clean copy to personal research while keeping client-specific annotations, highlights, and conclusions in the client record.<\/p>\n

    How should I handle a note that mixes client facts and general lessons?<\/h3>\n

    Split it instead of moving it whole. The original note, with its client facts, stays in the engagement record. If the general lesson passes the reuse gate, write it up as a new note in your personal knowledge base without carrying over client details. Splitting keeps the client material in one place and makes it clear which version is cleared for reuse.<\/p>\n

    What should happen to client files when an engagement ends?<\/h3>\n

    Follow the engagement terms first, since they may require you to return, delete, or keep certain records. If the files include sensitive consumer personal information, FTC business guidance favors keeping it only while a business reason exists and documenting how retained data is secured and disposed of. A separate client workspace makes this step simpler, because you can archive or delete one client’s material without sorting through your personal research.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Keep client files separate by sorting everything into three groups: client records, engagement working notes, and your own independent research. By default, only the third group belongs in a personal knowledge base. A client-derived insight should join it only after the engagement terms allow that reuse. Each group should live behind a boundary your tools […]<\/p>\n","protected":false},"author":3,"featured_media":3346,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3348","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":8}},"yoast_head":"\nSeparate Client Files From a Knowledge Base<\/title>\n<meta name=\"description\" content=\"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Separate Client Files From a Knowledge Base\" \/>\n<meta property=\"og:description\" content=\"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/\" \/>\n<meta property=\"og:site_name\" content=\"Olares Articles\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-26T12:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-27T06:50:26+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png\" \/>\n\t<meta property=\"og:image:width\" content=\"944\" \/>\n\t<meta property=\"og:image:height\" content=\"629\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Yajing Wang\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Olares_OS\" \/>\n<meta name=\"twitter:site\" content=\"@Olares_OS\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Yajing Wang\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/\"},\"author\":{\"name\":\"Yajing Wang\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/person\\\/d106d6ed3db3314a7a18162f8b4c27ae\"},\"headline\":\"How to Keep Client Files Separate From a Personal Knowledge Base\",\"datePublished\":\"2026-10-26T12:00:00+00:00\",\"dateModified\":\"2026-10-27T06:50:26+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/\"},\"wordCount\":1389,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/keep-client-files-separate-knowledge-base-featured.png\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/\",\"name\":\"Separate Client Files From a Knowledge Base\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/keep-client-files-separate-knowledge-base-featured.png\",\"datePublished\":\"2026-10-26T12:00:00+00:00\",\"dateModified\":\"2026-10-27T06:50:26+00:00\",\"description\":\"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/keep-client-files-separate-knowledge-base-featured.png\",\"contentUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/keep-client-files-separate-knowledge-base-featured.png\",\"width\":944,\"height\":629,\"caption\":\"A consultant sorts client records, engagement notes, and independent research into three separate groups.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/keep-client-files-separate-knowledge-base\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Keep Client Files Separate From a Personal Knowledge Base\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#website\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\",\"name\":\"Olares Articles\",\"description\":\"Perspectives on private AI, self-hosting, and a digital life you control.\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#organization\",\"name\":\"Olares\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/mascot_black.png\",\"contentUrl\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/mascot_black.png\",\"width\":1000,\"height\":1000,\"caption\":\"Olares\"},\"image\":{\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/people\\\/Olares\\\/61579156063357\\\/\",\"https:\\\/\\\/x.com\\\/Olares_OS\",\"https:\\\/\\\/github.com\\\/beclab\\\/Olares\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/olarestech\\\/\",\"https:\\\/\\\/www.youtube.com\\\/@OlaresOS\\\/featured\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/#\\\/schema\\\/person\\\/d106d6ed3db3314a7a18162f8b4c27ae\",\"name\":\"Yajing Wang\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g\",\"caption\":\"Yajing Wang\"},\"description\":\"Yajing Wang is Head of Growth at Olares. Yajing's work focuses on helping people understand personal cloud software, local AI, and self-hosted applications, with an emphasis on clear explanations of how these tools fit into everyday workflows.\",\"url\":\"https:\\\/\\\/www.olares.com\\\/articles\\\/author\\\/yajing-wang\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Separate Client Files From a Knowledge Base","description":"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/","og_locale":"en_US","og_type":"article","og_title":"Separate Client Files From a Knowledge Base","og_description":"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.","og_url":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/","og_site_name":"Olares Articles","article_publisher":"https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/","article_published_time":"2026-10-26T12:00:00+00:00","article_modified_time":"2026-10-27T06:50:26+00:00","og_image":[{"width":944,"height":629,"url":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png","type":"image\/png"}],"author":"Yajing Wang","twitter_card":"summary_large_image","twitter_creator":"@Olares_OS","twitter_site":"@Olares_OS","twitter_misc":{"Written by":"Yajing Wang","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#article","isPartOf":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/"},"author":{"name":"Yajing Wang","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/person\/d106d6ed3db3314a7a18162f8b4c27ae"},"headline":"How to Keep Client Files Separate From a Personal Knowledge Base","datePublished":"2026-10-26T12:00:00+00:00","dateModified":"2026-10-27T06:50:26+00:00","mainEntityOfPage":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/"},"wordCount":1389,"commentCount":0,"publisher":{"@id":"https:\/\/www.olares.com\/articles\/#organization"},"image":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#primaryimage"},"thumbnailUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/","url":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/","name":"Separate Client Files From a Knowledge Base","isPartOf":{"@id":"https:\/\/www.olares.com\/articles\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#primaryimage"},"image":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#primaryimage"},"thumbnailUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png","datePublished":"2026-10-26T12:00:00+00:00","dateModified":"2026-10-27T06:50:26+00:00","description":"Sort client records, engagement notes, and personal research into separate workspaces, then check access and indexing before reusing insights.","breadcrumb":{"@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#primaryimage","url":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png","contentUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/10\/keep-client-files-separate-knowledge-base-featured.png","width":944,"height":629,"caption":"A consultant sorts client records, engagement notes, and independent research into three separate groups."},{"@type":"BreadcrumbList","@id":"https:\/\/www.olares.com\/articles\/keep-client-files-separate-knowledge-base\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.olares.com\/articles\/"},{"@type":"ListItem","position":2,"name":"How to Keep Client Files Separate From a Personal Knowledge Base"}]},{"@type":"WebSite","@id":"https:\/\/www.olares.com\/articles\/#website","url":"https:\/\/www.olares.com\/articles\/","name":"Olares Articles","description":"Perspectives on private AI, self-hosting, and a digital life you control.","publisher":{"@id":"https:\/\/www.olares.com\/articles\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.olares.com\/articles\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.olares.com\/articles\/#organization","name":"Olares","url":"https:\/\/www.olares.com\/articles\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/logo\/image\/","url":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/09\/mascot_black.png","contentUrl":"https:\/\/www.olares.com\/articles\/wp-content\/uploads\/2026\/09\/mascot_black.png","width":1000,"height":1000,"caption":"Olares"},"image":{"@id":"https:\/\/www.olares.com\/articles\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/people\/Olares\/61579156063357\/","https:\/\/x.com\/Olares_OS","https:\/\/github.com\/beclab\/Olares","https:\/\/www.linkedin.com\/company\/olarestech\/","https:\/\/www.youtube.com\/@OlaresOS\/featured"]},{"@type":"Person","@id":"https:\/\/www.olares.com\/articles\/#\/schema\/person\/d106d6ed3db3314a7a18162f8b4c27ae","name":"Yajing Wang","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/e14488812ffef7f238774b577689ca193019f2bbb1c1745cde735ab71d3c4cbc?s=96&d=mm&r=g","caption":"Yajing Wang"},"description":"Yajing Wang is Head of Growth at Olares. Yajing's work focuses on helping people understand personal cloud software, local AI, and self-hosted applications, with an emphasis on clear explanations of how these tools fit into everyday workflows.","url":"https:\/\/www.olares.com\/articles\/author\/yajing-wang\/"}]}},"_links":{"self":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3348","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/comments?post=3348"}],"version-history":[{"count":2,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3348\/revisions"}],"predecessor-version":[{"id":3421,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/posts\/3348\/revisions\/3421"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/media\/3346"}],"wp:attachment":[{"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/media?parent=3348"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/categories?post=3348"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.olares.com\/articles\/wp-json\/wp\/v2\/tags?post=3348"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}