> 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/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/configurar-as-definicoes-de-apresentacao-do-portal.md).

# Configurar as definições de apresentação do Portal

Controlar quais páginas, registos e opções do Portal os Clientes podem ver.

O **Definições de Portal** Esta secção controla a visibilidade da informação no Portal.

Serve para manter o Portal relevante para o Cliente.

{% stepper %}
{% step %}

### Abrir o portal

Abrir o portal que se pretende editar.
{% endstep %}

{% step %}

### Abrir Definições de Portal

Selecionar **Definições de Portal** no menu lateral esquerdo.
{% endstep %}

{% step %}

### Rever as opções de visibilidade

Escolher as páginas e os dados a que os Clientes podem aceder.
{% endstep %}

{% step %}

### Decidir quais as ações permitidas

Definir opções como planeamento, histórico, acesso às Faturas e acesso à API.
{% endstep %}

{% step %}

### Guardar as Definições

Clicar em **Guardar**.
{% endstep %}
{% endstepper %}

### Opções comuns

* mostrar apenas as etapas relevantes da Encomenda
* ocultar Faturas ou Propostas quando não forem necessárias
* manter limitada a visibilidade do Objeto e do Projeto

### Perguntas frequentes

<details>

<summary>É possível mostrar Faturas mas ocultar Propostas?</summary>

Sim.

Essas opções são controladas separadamente.

</details>

<details>

<summary>Por que motivo ocultar informação no Portal?</summary>

Para manter o Portal claro e relevante.

</details>

<details>

<summary>É possível ativar o acesso à API aqui?</summary>

Sim.

Essa opção faz parte das Definições de Portal.

</details>

### Tópicos relacionados

* [**Portal de cliente**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente.md)
* [**Ativar o acesso à API do Portal**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/ativar-o-acesso-a-api-do-portal.md)
* [**Configurar as Definições facturação**](/outsmart-knowledge-base/outsmart-knowledge-base-pt/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/configurar-as-definicoes-facturacao.md)


---

# 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/loja-virtual-pacotes-e-power-ups/power-ups/portal-de-cliente/configurar-as-definicoes-de-apresentacao-do-portal.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.