---
title: Frequently Asked Questions
description: >-
  Documented answers on scope, modules, roles, relationships, metadata, and
  quality in GovFrame.
audiencia: Users and responsible parties evaluating or beginning to use GovFrame
roles: >-
  User | Data Steward | Data Owner | Data Engineer | Administrator |
  Superadministrator
modulo: Cross-cutting view of data governance
revision: '2026-10-19'
section: empezar
order: 30
sources:
  - CONTEXT.md
  - Modelodeobjetosyrelaciones.md
  - Módulosydependencias.md
  - 'Roles,capacidadesyalcance.md'
  - Cómoleerelmapaderelaciones.md
locale: en
---
# Frequently Asked Questions

These answers describe GovFrame’s documented behavior. Availability depends on the active company, membership, role, scope, and enabled modules. If there is no evidence of a specific configuration, the limit is stated rather than assumed.

## Before you begin

Check that you are working in the correct company and that its status allows normal operations. A person may belong to several companies, with their role and scope resolved in each one. If you cannot act on an object, check capability, scope, and module—not just whether a button is visible.

## Frequently Asked Questions

### What problem does GovFrame help solve?

It organizes a consolidated view of data governance: existing information, definitions, owners, technical location, controls, products, contracts, and pending work. The taxonomy provides the common framework for connecting these elements without turning them into a flat catalog.

### What is the basic catalog structure?

The company can use **Domain → Entity → Attribute** or add an optional **Subdomain**. Domain expresses the broad area and responsibility; Attribute is the level at which many rules and technical fields are associated. Other objects may have a direct, component-based, inherited, or derived through composition association.

### Does a role grant access to the entire company?

No. GovFrame separates tenant role, capability, and scope. Data Owners and Data Stewards need the authorized Domain or Subdomain; Data Engineers work on Repositories with an active technical scope. The Administrator has global scope within the active company. The Superadministrator operates at a different layer and maintains the safeguards for company objects.

### Why might a function be unavailable or reject an operation?

Modules are configured per company. If a module is disabled, it cannot be operated, and the backend rejects its procedures; reaching a route directly is not enough. Disabling a module does not delete existing data. Check dependencies before basing a process on a related function.

### Which connectors are documented?

The current model documents connectors for PostgreSQL, BigQuery, SingleStore, and Power BI Service. A Repository provides context for metadata and the Technical Dictionary; technical relationships remain subject to the Data Engineer’s scope and the company’s configuration.

### Does a table or Repository mean that all its fields are governed?

No. A Repository may exist without all its fields being registered in the Technical Dictionary or associated with Attributes. A high-level relationship with a Domain also does not automatically associate all the fields in a source with all the Attributes in that scope.

### When can SQL be generated for a quality rule?

A Quality Rule is associated with an Attribute. SQL can only be generated when valid associations to physical fields exist and a dialect is configured. Generation does not mean automatic execution, and this documentation does not confirm scheduled execution of rules.

### How does metadata synchronization work?

The configuration may provide for a manual, daily, weekly, or monthly schedule, previews, and versioned snapshots, including detection of changes to tables and columns. The effective schedule depends on each company: automated or production jobs are not assumed to be enabled.

### Does GovFrame have independent Risks and Controls catalogs?

Not in the current model. A control is represented, as needed, by a Quality Rule, a Policy or Procedure, a Workflow, a task, an approval, a classification, a certification, or a rule included in a Contract. Risks, alerts, or coverage may appear as derived information; they should not be documented as independent inventories.

### What does the Relationship Explorer show?

It starts from the taxonomy and offers Overview to discover the ecosystem, Impact to follow registered dependencies, and Technical Detail to inspect the link between Attributes, fields, Repositories, and Systems. A missing line is not filled in by inference: it indicates that no relationship is registered.

### What happens to data when a module is disabled?

The data is retained but remains outside visible operations until the module is reactivated, in accordance with company policy. Reactivation remains subject to visibility and operation being governed by roles, scope, and valid relationships.

### Which company statuses are documented?

Only `provisioning`, `active`, `suspended`, `disabled`, and `deprovisioned`. Normal operations are permitted for an active company. This page does not define statuses for other objects.

## Recommended path

To turn these answers into a practical action, start with a Domain, assign owners and scope, document Entities and Attributes, and add a technical link only when a Repository exists and a verifiable physical association is available. Then add rules, products, contracts, or tracking mechanisms that are enabled and have a documented relationship.

## Expected outcome

You should be able to identify which data is governed in an initial scope, who can act on it, and which business or technical relationships are actually registered. If an answer depends on local configuration—for example, a module or schedule—confirm it with the company’s authorized administration.

## Reference materials

- [Object and relationship model](/en/explicaciones/modelo-de-objetos-y-relaciones/)
- [How to read the relationship map](/en/guias/como-leer-mapa-de-relaciones/)
- [Roles, capabilities, and scope](/en/referencia/roles-capacidades-y-alcance/)
- [Modules and dependencies](/en/referencia/modulos-y-dependencias/)
