> 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/portals-and-interfaces/central-portal.md). # Central Portal The Central Portal is the platform operator's console. It is where tenants are onboarded, third parties are governed, APIs are published and managed, and the health of the whole platform is observed. ## Tenant management Onboard a bank by creating a tenant record and nominating its first Bank Portal administrators. Creation and every subsequent edit is submitted for approval by a second administrator before taking effect. Tenant status controls both the bank's own administrative access and its third parties' access to live APIs. ## Third-party management Central Administration Portal is a place where you manage your TPPs. The following information for every TPP is available: | Section | Contents | | ------------------- | ----------------------------------------------------------------------------------------------- | | General information | Legal and contact details | | Sandbox limits | Per-product call limits in the sandbox; left blank, a product is unlimited | | Certificates | Active certificates uploaded through the Developer Portal, with test certificates distinguished | | Aggregation | Aggregated products granted, with limits and tariffs | | Subscriptions | Every subscription held, and its state | The operator can change a third party's status, edit its details and sandbox limits, as well as manage its Superusers. A full revision history is retained, and pending changes are indicated on the record. ## Subscription management Manage subscriptions to your own API products — give/remove access to a product, set call limits and tariffs. ## API management Publishing, versioning and policy configuration, restricted to the API manager role. This is where OpenAPI specifications are uploaded and preprocessed, version statuses are promoted, policies are assigned, and back-office integrations are configured. ## Content management Editing the developer-facing portal, restricted to the CMS Manager role, with its own review flow and preview. In multi-tenant deployments every tenant's portal is listed and edited separately. ## Reporting and oversight Platform-wide usage by tenant and by third party, cross-tenant aggregates, error breakdowns, billing volumes and total throughput. Together with availability monitoring, this is the operator's view of whether the platform is meeting its obligations. --- # 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/portals-and-interfaces/central-portal.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.