> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/architecture-and-security.md).

# ARCHITECTURE AND SECURITY

- [Anomaly Detection](https://docs.apono.io/docs/architecture-and-security/anomalies.md): Safeguard against potential risky access to your tools
- [Multi-factor Authentication](https://docs.apono.io/docs/architecture-and-security/multi-factor-authentication.md): Safeguard against potential unauthorized access to your tools
- [Credentials Rotation Policy](https://docs.apono.io/docs/architecture-and-security/credentials-rotation-policy.md): Use Apono for periodic credentials rotation and passwords reset on granted access for security and compliance purposes
- [Periodic User Cleanup & Deletion](https://docs.apono.io/docs/architecture-and-security/periodic-user-cleanup-and-deletion.md): Use Apono's periodic user cleanup by deleting inactive users for security and compliance purposes
- [End-user Authentication](https://docs.apono.io/docs/architecture-and-security/authentication-types.md): Specify integration-specific user authentication for end-users to use their granted access
- [Personal API Tokens](https://docs.apono.io/docs/architecture-and-security/personal-api-tokens.md): Learn how to create and delete personal API tokens
- [Apono Account Token](https://docs.apono.io/docs/architecture-and-security/apono-service-account.md): Learn how to create and manage service account API tokens
- [Account Settings](https://docs.apono.io/docs/architecture-and-security/account-settings.md): Manage account-level settings and feature controls


---

# 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://docs.apono.io/docs/architecture-and-security.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.