> 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/access-control.md).

# Access Control

Every portal enforces role-based access with least privilege, and the roles are fixed rather than freely composed — which makes access reviews tractable and keeps separation of duties intact.

## Authentication

Users do not self-register except for the first user of a third-party organization. Everyone else is invited by email, and activation is a defined sequence: follow the invitation link, set a password, register an authenticator device, complete the profile, sign in.

**Two-factor authentication is mandatory.** A time-based one-time password app such as Google Authenticator or FreeOTP is registered at activation, and users can manage their own devices afterwards. Identity is handled by a dedicated identity provider component; invitation links are time-limited.

Users hold one of three statuses — Pending, Active or Suspended — and only Active users can sign in. Suspension is immediate and reversible, which is the right tool when someone leaves a role rather than an organization.

## Separation of duties

The model is deliberately constrained in ways that matter for audit.

* **No self-elevation.** A User Administrator cannot grant the User Administrator role to anyone, and a bank Superuser cannot create another Superuser — that remains with the platform operator. Privilege escalation therefore always involves a second party.
* **Four eyes on consequential change.** Tenants, subscriptions and published content require an editor and a separate approving supervisor. Approval requests carry a justification, and rejections require a comment.
* **Tenant boundaries.** A bank's administrators can only nominate reviewers within their own bank, and cannot see another tenant's users, consents or terms.
* **Approval privacy.** Operator and bank see each other's approved changes only — never each other's pending or rejected ones.
* **Bank administrators are provisioned through the tenant agreement,** not the user list, so adding or removing one is itself a reviewed change.

## Audit

User management actions are written to a dedicated audit index, separately from application logging, and every API exchange is recorded with a shared trace identifier linking the records belonging to one call. Audit retention is configurable and typically held hot for months before archiving. Deleting a third party, user or tenant erases the record and anonymizes the corresponding audit trail, which is what allows an erasure request to be honored without destroying the audit history.


---

# 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/access-control.md?ask=<question>&goal=<user_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.
