> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/agency/es/what-would-you-like-to-learn-about/brand-and-partner-management/resolve-the-access-denied-error-as-an-agency.md).

# Resolver el error “Acceso denegado” como agencia

Si eres una agencia y te has suscrito a los correos electrónicos semanales de merchandising de impact.com, podrías encontrarte con un error de Acceso denegado cuando selecciones un enlace a una lista seleccionada por un editor. Esto ocurre porque estas listas solo son accesibles para cuentas de marca.

Hay una solución rápida: inicia sesión en una de tus cuentas de marca antes de hacer clic en el enlace. Esta breve guía te mostrará cómo.

1. Inicia sesión en tu consola de agencia en impact.com.
2. En el menú de navegación de la izquierda, selecciona ![](https://2281609684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTNfAIjBtFchXJ9pC2q%2Fuploads%2Fgit-blob-b60d1cf660bd56d7d450f97f940d927512146703%2F979eb643f9453e9255704627c05f2d1af22503c6fb50cc69df3972fa95e96f73.svg?alt=media) **\[Agencia] → Anunciantes**.
3. Selecciona **Iniciar sesión** para iniciar sesión como una de tus marcas gestionadas.

Se te redirigirá a la vista de marca de la plataforma impact.com. Desde aquí, puedes volver al correo electrónico y seleccionar el enlace de nuevo para ver la lista en Marketplace.


---

# 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://help.impact.com/agency/es/what-would-you-like-to-learn-about/brand-and-partner-management/resolve-the-access-denied-error-as-an-agency.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.