> For the complete documentation index, see [llms.txt](https://docs.cloudeka.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.id/support/deka-manage-service.md).

# Deka Manage Service

**Deka Manage Service** this menu is used to purchase Cloudeka Portal Service packages that have been provided, create, and view tickets that have already been made. It can be understood as follows:

1. On **project** with **Postpaid type** that use **payment method** is **Fixed** must purchase Package in Manage Service to use the Create Ticket service on the List Tickets menu.
2. On **project** with **Postpaid Usage Based type** that use **payment method** is **Pay Per Use** it can create a Create Ticket on the List Tickets menu without having to purchase Package in Manage Service.
3. On **project** with **Prepaid type** that use **payment method** is **Pay Per Use** it can create a Create Ticket on the List Tickets menu without having to purchase Package in Manage Service.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cloudeka.id/support/deka-manage-service.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.