> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/product-guides/compliance-studio.md).

# Compliance Studio

- [Workflows](https://docs.complycube.com/documentation/product-guides/compliance-studio/workflows.md): Build KYC onboarding flows with integrated AML screening. Orchestrate identity verification, liveness checks, dynamic questionnaires, and more in a single verification journey.
- [Smart Forms](https://docs.complycube.com/documentation/product-guides/compliance-studio/smart-forms.md): Dynamic questionnaires for KYC onboarding. Capture customer data, compliance declarations, and supporting documents inside verification workflows.
- [eSignatures](https://docs.complycube.com/documentation/product-guides/compliance-studio/e-signatures.md): Electronic signatures for KYC, AML, and customer onboarding workflows. Create document templates, capture legally binding signatures, and support eIDAS signature levels including SES, AdES, and QES.
- [Compliance Policies](https://docs.complycube.com/documentation/product-guides/compliance-studio/policies.md): Automate KYC/AML compliance with regulatory and custom policies inside workflows. Get real-time policy evaluation, rule-based decisions, and audit-ready evidence.
- [Regulatory coverage](https://docs.complycube.com/documentation/product-guides/compliance-studio/policies/regulatory-coverage.md): Explore ComplyCube’s compliance policy coverage across global frameworks, national regulations, and industry requirements, with support for policies across KYC, IDV, AML, CDD, and EDD.


---

# 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.complycube.com/documentation/product-guides/compliance-studio.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.