> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/timesheet/horas-do-timesheet.md).

# Horas do TimeSheet

Usar o temporizador ou a introdução manual para criar lançamentos de horas no TimeSheet.

## TimeSheet Horas

Usar **TimeSheet Horas** para registar períodos de trabalho em TimeSheet.

O fluxo do temporizador é o ponto de entrada principal.

### O que se pode fazer

* iniciar e Parar o temporizador
* Criar entradas de hora a partir de um temporizador parado
* Rever as entradas na Semana selecionada

{% stepper %}
{% step %}

### Abrir **Horas**

Abrir **TimeSheet**, depois escolher **Horas**.
{% endstep %}

{% step %}

### Iniciar ou adicionar tempo

Iniciar o temporizador ou Criar um Novo registo manualmente.
{% endstep %}

{% step %}

### Guardar o registo

Parar o temporizador ou guardar o registo para que apareça na vista da Semana.
{% endstep %}
{% endstepper %}

### É importante ter em conta

Parar o temporizador abre o fluxo de criação de hora.


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/timesheet/horas-do-timesheet.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.