> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/features/content-management.md). # Content Management The [Developer Portal](/portals-and-interfaces/developer-portal.md) portal is the shop window, and its content belongs to you. A built-in content management system lets the Platform operator maintain it directly via [Central Administration Portal](/portals-and-interfaces/central-portal.md), with the same review discipline applied to it as to any other consequential change. ## Multi-tenant deployments Where each tenant has its own Developer Portal, the CMS offers a separate editing entry point for every portal. Content is therefore maintained per tenant, and a change to one bank's landing page has no effect on another's. ## What can be edited The CMS allows to edit the contents of the public part of the Developer Portal. Beyond text, the CMS controls the product catalog: product cards can be added and removed, which allows to promote newly published API product. Terms of use and privacy notices are modifiable via CMS. The CMS Manager can also publish notices to third-party providers on the portal. This is the intended route for announcing planned maintenance, a deprecation, or a live incident — the audience is exactly the population that needs to know, and it requires no release. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.api.tieto.com/features/content-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.