> 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/definicoes/competencias.md).

# Competências

Escolher a Competência usada para as Horas e definir uma Competência predefinida.

## Competências

### Competências

**Competências** determinam os Tipos de hora Disponível durante o registo de tempo. A Empresa define as Competências no Backoffice.

### Escolher uma Competência para um período de trabalho

Quando existem várias Competências, o **Competência** campo aparece. Escolher a Competência que corresponde ao trabalho. Os Tipos de hora Disponível são então actualizados.

### Definir uma competência predefinida

{% stepper %}
{% step %}

#### Abrir Definições da app

Ir para **Definições > Definições da app**.
{% endstep %}

{% step %}

#### Escolher a predefinição

Tocar **Competências** e escolher a competência predefinida.
{% endstep %}
{% endstepper %}

### Tenha em conta

* O campo Competência só aparece quando existem mais do que uma competência.
* As Competências sem Tipos de hora mantêm-se ocultas.
* Adicionar Tipos de hora no Backoffice quando necessário.


---

# 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/definicoes/competencias.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.