> For the complete documentation index, see [llms.txt](https://docs.travelauthority.gov.zm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.travelauthority.gov.zm/readme.md). # Welcome Aboard The Travel Authority System (TAS) is a digital platform designed to streamline the process of requesting, reviewing, approving, and monitoring official government travel and workshop activities. The system provides a centralized environment where **public service officers** can submit requests, while **authorized personnel** review, approve, or return them for correction in accordance with established procedures. By digitizing this process, TAS improves: * Efficiency in request handling * Transparency in approvals * Accountability in travel-related decisions * Access to real-time reporting and insights ## **Jump Right In**
Cover image

:plane-departure:

Getting StartedCreate and submit your first travel request in a few steps.Getting StartedSelect Country.png

:window:

System OverviewLearn how the system is structured and how to navigate it effectively.Your first projectDashboard.png

:key:

User Roles and PermissionsLearn how access is controlled within the system.API ReferenceLogin.png

:file-lines:

Request ManagementCreate, track and manage requests through a structured workflow, from submission to approval.Request Details.png
*** {% columns %} {% column width="50%" %}
{% endcolumn %} {% column width="50%" valign="middle" %} ## **Learn More About System Configuration** Read guides, watch tutorials, and learn more about how to tailor the system to your organization. Guides Documentation {% endcolumn %} {% endcolumns %} --- # 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.travelauthority.gov.zm/readme.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.