> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-desktop/es/administracion/database-visibility.md).

# Visibilidad de la Base de datos

## Visibilidad de Base de datos y control de acceso

Existen dos Tipos de Visibilidad de Base de datos:

Las Bases de datos del Sistema se recomiendan para configuraciones cliente-servidor y se han creado mediante `Pestaña Sistema > Bases de datos del Sistema > Crear conexión con base de datos`.

Las conexiones de base de datos Definir usuario solo son visibles para el Usuario que las ha creado.

El complemento GeoDin Ground para Civil 3D solo muestra los Proyectos a los que el Usuario tiene acceso en la Base de datos, lo que implica control de acceso a nivel de base de datos.

A los Usuarios de GeoDin Ground se les debe conceder explícitamente acceso a la Base de datos antes de que puedan importar datos del Proyecto.


---

# 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.geodin.com/geodin-desktop/es/administracion/database-visibility.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.