> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Elofy as a data source
> Bring data from Elofy to your Lakehouse.
Elofy is a Brazilian people management platform covering performance reviews, OKRs and goals, individual development plans (IDPs), 1-on-1 meetings, feedback, praise and engagement surveys. Nekt extracts this data through the Elofy open data API.
## Configuring Elofy as a Source
In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Elofy option from the list of connectors.
Click **Next** and you'll be prompted to add your access.
### 1. Add account access
The token comes from your own Elofy account. In Elofy, go to **Configurações > Integrações e API** and copy the value of **"Token API Pública - Dados dos módulos"**.
The token must belong to a user whose **only** profile is administrator. Elofy rejects API requests from users with more than one profile attached (for example manager and administrator).
The following configuration is required:
* **API Token**: The public API token copied from Configurações > Integrações e API.
Optionally, under advanced settings:
* **Start Date**: The earliest date used by the streams that require an explicit date range (Individual Development Plans). When omitted, the full history is fetched.
* **Updated Since**: Only fetches records updated on or after this date, using the API's `updatedAt` filter. Useful to bound the volume of large streams. When omitted, every stream reads its full history.
* **Page Size**: Number of records requested per page (defaults to 500). Lower it if Elofy times out on large streams.
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Elofy exposes data per module, and the API only returns what your profile has permission to access. If your company does not use a given module — succession, surveys or nine-box, for example — its streams return no data, and the extraction continues without failing.
> Tip: The stream can be found more easily by typing its name.
Select the streams and click **Next**.
### 3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
* Incremental: every time the extraction happens, we'll get only the new data - which is good if, for example, you want to keep every record ever fetched.
* Full table: every time the extraction happens, we'll get the current state of the data - which is good if, for example, you don't want to have deleted data in your catalog.
The Elofy API does not return a last-modified timestamp on its records, so every stream is extracted as a full table. Use the **Updated Since** setting if you need to limit how far back each extraction reads.
Once you are done configuring, click **Next**.
### 4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters.
To define your [Trigger](https://docs.nekt.com/get-started/core-concepts/triggers), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).
Once you are ready, click **Next** to finalize the setup.
### 5. Check your new source
You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.
# Streams and Fields
Below you'll find all available data streams from Elofy and their corresponding fields. All streams are extracted as full tables. Column names are normalized to snake\_case, since the Elofy API returns field names in mixed formats.
Some streams depend on another one to know what to request: the performance review and goal streams are extracted once per period, the survey answer streams once per survey, and the detailed review stream once per configured review cycle. Nekt resolves those automatically.
## Organization
Company registered in Elofy, with its economic group.
Table: `company`
**Key Fields:**
* `id_empresa` - Identifier of the company the record belongs to.
* `nome_da_empresa` - Name of the company the record belongs to.
* `id_grupo_economico` - Identifier of the economic group the company belongs to.
Employees registered in Elofy, with team, job position, manager and access profiles.
Table: `users`
**Key Fields:**
* `id_usuario` - Identifier of the user.
* `nome_usuario` - Name of the user.
* `matricula` - Employee registration number (matrícula) of the user.
* `status` - Current status of the record.
* `data_de_admissao` - Date the employee was hired.
* `data_de_deligamento` - Date the employee was offboarded, when applicable.
* `id_gestor` - Identifier of the manager.
* `gestor` - Name of the manager.
* `email` - Email address of the user.
* `login` - Login used by the user to access Elofy.
* `tipo_cargo` - Type of the job position (for example leadership or individual contributor).
* `id_cargo` - Identifier of the job position.
Teams of the organizational structure, including the parent team hierarchy.
Table: `teams`
**Key Fields:**
* `id_time` - Identifier of the team.
* `time` - Name of the team the employee belongs to.
* `status` - Current status of the record.
* `codigo_time_sistema_origem` - Team code in the HR system that feeds Elofy.
* `id_usuario_responsavel` - Identifier of the user responsible for the team.
* `usuarios_responsavel` - Users responsible for the team.
* `id_time_pai` - Identifier of the parent team.
* `time_pai` - Name of the parent team in the organizational hierarchy.
* `ids_tags` - Comma-separated identifiers of the tags linked to the record.
* `tags` - Tags linked to the record.
Job positions, with replacement difficulty, business impact and succession mapping.
Table: `positions`
**Key Fields:**
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
* `status` - Current status of the record.
* `codigo_cargo_sistema_origem` - Job position code in the HR system that feeds Elofy.
* `descricao` - Free-text description of the record.
* `dificuldade` - How hard the job position is to replace.
* `impacto` - Business impact of the job position.
* `mapeado_para_sucessao` - Whether the job position is mapped for succession planning.
* `regua` - Rating scale (régua) applied to the record.
Competency library, with expected behaviours and the teams and positions it applies to.
Table: `competencies`
**Key Fields:**
* `id_competencia` - Identifier of the competency.
* `competencia` - Name of the competency.
* `categoria_competencia` - Category the competency is grouped under.
* `descricao` - Free-text description of the record.
* `ids_times` - Comma-separated identifiers of the teams the competency applies to.
* `nomes_times` - Names of the teams the competency applies to.
* `ids_cargos` - Comma-separated identifiers of the job positions the competency applies to.
* `nomes_cargos` - Names of the job positions the competency applies to.
* `esperado` - Behaviour expected from employees on this competency.
* `o_que_queremos` - Behaviours the company wants to see on this competency.
* `o_que_nao_queremos` - Behaviours the company does not want to see on this competency.
* `comportamentos` - Observable behaviours described for the competency.
## Periods and cycles
Periods (planning windows) in Elofy. Their ids drive the period-filtered streams.
Table: `periods`
**Key Fields:**
* `id_periodo` - Identifier of the period.
* `periodo` - Name of the period the record belongs to.
* `data_de_inicio` - Date the period or cycle starts.
* `data_de_fim` - Date the period or cycle ends.
* `situacao` - Current state of the record as shown in Elofy.
* `escala_de_peso_de_objetivos` - Weight scale applied to objectives in the period.
* `nome_padrao_de_objetivo` - Default label used for objectives in the period.
* `escala_de_peso_de_resultados_chave` - Weight scale applied to key results in the period.
* `periodicidade_padrao_resultados_chave` - Default measurement frequency for key results in the period.
* `modulo` - Elofy module the record belongs to.
Periods with the full module configuration and volume counters of each one.
Table: `periods_detailed`
**Key Fields:**
* `id_periodo` - Identifier of the period.
* `nome_empresa` - Name of the company the record belongs to.
* `periodo` - Name of the period the record belongs to.
* `data_inicial_periodo` - Date the period starts.
* `data_final_periodo` - Date the period ends.
* `escala_pesos_kr` - Weight scale applied to key results in the period.
* `escala_pesos_meta` - Weight scale applied to goals in the period.
* `possui_ciclo_competencias` - Whether the period includes a competency cycle.
* `ciclos_com_competencias` - Cycles of the period that include a competency evaluation.
* `amplitude_competencia` - Score range used by the competency cycle.
* `possui_ciclo_potencial` - Whether the period includes a potential cycle.
* `ciclos_com_potencial` - Cycles of the period that include a potential evaluation.
Cycles inside each period, with their start and end dates and status.
Table: `cycles`
**Key Fields:**
* `id_ciclo` - Identifier of the cycle.
* `ciclo` - Name of the cycle.
* `id_periodo` - Identifier of the period.
* `data_de_inicio` - Date the period or cycle starts.
* `data_de_fim` - Date the period or cycle ends.
* `situacao` - Current state of the record as shown in Elofy.
* `status` - Current status of the record.
## Goals and OKRs
Objectives of each period, with owner, driver, parent objective, weight and progress. Extracted once per period registered in Elofy.
Table: `objectives`
**Key Fields:**
* `id_objetivo` - Identifier of the objective.
* `id_periodo` - Identifier of the period.
* `periodo` - Name of the period the record belongs to.
* `id_ciclo` - Identifier of the cycle.
* `ciclo` - Name of the cycle.
* `id_direcionador` - Identifier of the strategic driver.
* `direcionador` - Name of the strategic driver.
* `id_objetivo_pai` - Identifier of the parent objective.
* `objetivo_pai` - Name of the parent objective.
* `objetivo` - Name of the objective.
* `objetivo_estrategico` - Whether the objective is a strategic one.
* `descricao` - Free-text description of the record.
Key results of the objectives, with baseline, target, latest measurement and progress. Extracted once per period registered in Elofy.
Table: `key_results`
**Key Fields:**
* `id_resultado_chave` - Identifier of the key result.
* `id_objetivo` - Identifier of the objective.
* `resultado_chave` - Name of the key result.
* `descricao` - Free-text description of the record.
* `workflow` - Approval workflow stage of the record.
* `id_responsavel` - Identifier of the owner.
* `responsavel` - Name of the owner of the record.
* `id_corresponsavel` - Identifier of the co-owner.
* `corresponsavel` - Name of the co-owner of the record.
* `peso` - Relative weight of the record in the score calculation.
* `unidade_de_medida` - Unit of measurement of the key result.
* `meta` - Target value defined for the record.
Objectives in the V2 payload, carrying their key results and co-owners inline. Extracted once per period registered in Elofy.
Table: `okrs_v2`
**Key Fields:**
* `id_objetivo` - Identifier of the objective.
* `nome_empresa` - Name of the company the record belongs to.
* `nome_objetivo` - Name of the objective.
* `ativo` - Whether the record is currently active.
* `workflow` - Approval workflow stage of the record.
* `id_responsavel` - Identifier of the owner.
* `nome_responsavel` - Name of the owner.
* `matricula_responsavel` - Employee registration number (matrícula) of the owner.
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
* `nivel_responsabilidade` - Responsibility level assigned to the job position.
* `id_time_responsavel` - Identifier of the owner's team.
Goal contracts (contrato de metas) in the V2 payload, carrying their goals inline. Extracted once per period registered in Elofy.
Table: `goals_contract_v2`
**Key Fields:**
* `id_objetivo` - Identifier of the objective.
* `nome_empresa` - Name of the company the record belongs to.
* `nome_objetivo` - Name of the objective.
* `ativo` - Whether the record is currently active.
* `workflow` - Approval workflow stage of the record.
* `id_responsavel` - Identifier of the owner.
* `nome_responsavel` - Name of the owner.
* `matricula_responsavel` - Employee registration number (matrícula) of the owner.
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
* `nivel_responsabilidade` - Responsibility level assigned to the job position.
* `id_time_responsavel` - Identifier of the owner's team.
Strategic drivers, with owner, progress and the objectives and goals linked to them.
Table: `drivers`
**Key Fields:**
* `id_direcionador` - Identifier of the strategic driver.
* `nome_empresa` - Name of the company the record belongs to.
* `id_periodo` - Identifier of the period.
* `nome_periodo` - Name of the period the record belongs to.
* `nome_direcionador` - Name of the strategic driver.
* `progresso_direcionador` - Current progress of the strategic driver, as a percentage.
* `descricao_direcionador` - Description of the strategic driver.
* `responsavel` - Name of the owner of the record.
* `nome_responsavel` - Name of the owner.
* `matricula_responsavel` - Employee registration number (matrícula) of the owner.
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
Indicator library, with the monthly goal and check-in values of each indicator.
Table: `base_indicators`
**Key Fields:**
* `id_indicador` - Identifier of the indicator.
* `nome_empresa` - Name of the company the record belongs to.
* `nome_indicador` - Name of the indicator.
* `descricao` - Free-text description of the record.
* `ativo` - Whether the record is currently active.
* `dimensao` - Dimension the indicator is classified under.
* `origem` - Where the record originated (for example manual creation or an integration).
* `peso` - Relative weight of the record in the score calculation.
* `tipo_informacao` - Kind of value tracked by the indicator (for example number or percentage).
* `forma_calculo` - Formula used to calculate the indicator progress.
* `tipo_score` - Score calculation type applied to the record.
* `id_periodo` - Identifier of the period.
## Performance review
Performance review setup, one row per review phase, with the rules enabled for it.
Table: `cycle_review_config`
**Key Fields:**
* `nome_empresa` - Name of the company the record belongs to.
* `id_revisao` - Identifier of the cycle review.
* `nome_ciclo` - Name of the cycle.
* `id_ciclo` - Identifier of the cycle.
* `nome_revisao_de_ciclo` - Name of the cycle review.
* `status_revisao_de_ciclo` - Current status of the cycle review.
* `liberacao_de_notas` - Whether scores have been released to employees.
* `calibracao_de_notas` - Whether score calibration is enabled for the cycle review.
* `responder_avaliacoes` - Whether participants can still answer evaluations.
* `ano` - Year the cycle review refers to.
* `janela` - Evaluation window the cycle review belongs to.
* `trimestre_inicio` - Quarter the cycle review starts in.
Detailed performance review, one row per evaluation, with phases and scored items inline. Extracted once per configured cycle review.
Table: `cycle_review_detailed`
**Key Fields:**
* `id_revisao_ciclo` - Identifier of the cycle review.
* `ano` - Year the cycle review refers to.
* `nome_ciclo` - Name of the cycle.
* `id_revisao_ciclos_avaliacoes` - Identifier of the cycle review evaluation.
* `id_avaliado` - Identifier of the evaluated employee.
* `matricula_avaliado` - Employee registration number (matrícula) of the evaluated employee.
* `nome_avaliado` - Name of the evaluated employee.
* `id_time_avaliado` - Identifier of the evaluated employee's team.
* `nome_time_avaliado` - Name of the evaluated employee's team.
* `tipo_cargo_avaliado` - Type of the evaluated employee's job position.
* `id_tipo_cargo_avaliado` - Identifier of the evaluated employee's job position type.
* `id_cargo_avaliado` - Identifier of the evaluated employee's job position.
Performance review audience, with the phase averages of each evaluated employee. Extracted once per period registered in Elofy.
Table: `cycle_review_public`
**Key Fields:**
* `id_revisao_de_ciclo_score` - Identifier of the cycle review score.
* `id_revisao_de_ciclo` - Identifier of the cycle review.
* `nome_revisao_de_ciclo` - Name of the cycle review.
* `id_usuario_avaliado` - Identifier of the evaluated employee.
* `matricula_usuario_avaliado` - Employee registration number (matrícula) of the evaluated employee.
* `nome_usuario_avaliado` - Name of the evaluated employee.
* `status_usuario_avaliado` - Status of the evaluated employee in the cycle.
* `media_final` - Final average score of the evaluated employee.
* `fase` - Evaluation phase the row refers to.
* `media_fase` - Average score of the evaluation phase.
* `media_fase_auto` - Average of the evaluation phase coming from the self-evaluation.
* `media_fase_gestor` - Average of the evaluation phase coming from the manager's evaluation.
Performance review scores per phase, broken down by evaluation source and rating label. Extracted once per period registered in Elofy.
Table: `cycle_review_public_note_step`
**Key Fields:**
* `id_revisao_ciclo_score` - Identifier of the cycle review score.
* `id_revisao_ciclo` - Identifier of the cycle review.
* `nome_revisao_ciclo` - Name of the cycle review.
* `id_usuario_avaliado` - Identifier of the evaluated employee.
* `nome_usuario` - Name of the user.
* `status_usuario_avaliado` - Status of the evaluated employee in the cycle.
* `id_gestor` - Identifier of the manager.
* `nome_gestor` - Name of the manager.
* `media_final_ciclo` - Final average score of the employee in the cycle.
* `conceito_final_ciclo` - Final rating label of the employee in the cycle.
* `conceito_final_ciclo_calibrado` - Final rating label of the employee in the cycle after calibration.
* `nine_box` - Nine-box matrix the employee was placed in.
Competency phase averages of the performance review, per evaluated employee. Extracted once per period registered in Elofy.
Table: `cycle_review_average_step_competencies`
**Key Fields:**
* `id_revisao_ciclo_score` - Identifier of the cycle review score.
* `id_revisao_ciclo` - Identifier of the cycle review.
* `nome_revisao_ciclo` - Name of the cycle review.
* `periodo` - Name of the period the record belongs to.
* `id_usuario_avaliado` - Identifier of the evaluated employee.
* `nome_usuario_avaliado` - Name of the evaluated employee.
* `id_gestor` - Identifier of the manager.
* `nome_gestor` - Name of the manager.
* `conceito_final_ciclo` - Final rating label of the employee in the cycle.
* `media_final_ciclo_calibrado` - Final average score of the employee in the cycle after calibration.
* `conceito_final_ciclo_calibrado` - Final rating label of the employee in the cycle after calibration.
* `media_competencia` - Average competency score of the employee.
Results phase averages of the performance review, per evaluated employee and item. Extracted once per period registered in Elofy.
Table: `cycle_review_average_step_results`
**Key Fields:**
* `id_revisao_ciclo_avaliacoes_fase` - Identifier of the cycle review phase evaluation.
* `id_revisao_ciclo` - Identifier of the cycle review.
* `nome_revisao_ciclo` - Name of the cycle review.
* `id_usuario_avaliado` - Identifier of the evaluated employee.
* `nome_usuario_avaliado` - Name of the evaluated employee.
* `id_gestor` - Identifier of the manager.
* `nome_gestor` - Name of the manager.
* `conceito_final_ciclo` - Final rating label of the employee in the cycle.
* `media_final_ciclo_calibrado` - Final average score of the employee in the cycle after calibration.
* `conceito_final_ciclo_calibrado` - Final rating label of the employee in the cycle after calibration.
* `media_final_fase_resultados` - Final average score of the results phase.
* `item_avaliado` - Item that was evaluated in the phase.
Nine-box placement of each evaluated employee, before and after calibration. Extracted once per period registered in Elofy.
Table: `cycle_review_ninebox`
**Key Fields:**
* `id_revisao_ciclo_score` - Identifier of the cycle review score.
* `id_revisao_ciclo` - Identifier of the cycle review.
* `periodo` - Name of the period the record belongs to.
* `nome_revisao_ciclo` - Name of the cycle review.
* `data_inicio` - Start date of the record.
* `data_fim` - End date of the record.
* `id_usuario_avaliado` - Identifier of the evaluated employee.
* `nome_usuario_avaliado` - Name of the evaluated employee.
* `status_usuario_avaliado` - Status of the evaluated employee in the cycle.
* `id_gestor` - Identifier of the manager.
* `nome_gestor` - Name of the manager.
* `media_final_ciclo` - Final average score of the employee in the cycle.
## Development
IDPs (individual development plans), one row per plan initiative. Extracted over the date window defined by the Start Date setting.
Table: `pdi`
**Key Fields:**
* `id_responsavel` - Identifier of the owner.
* `matricula` - Employee registration number (matrícula) of the user.
* `responsavel` - Name of the owner of the record.
* `id_pdi` - Identifier of the IDP (individual development plan).
* `titulo_pdi` - Title of the IDP (individual development plan).
* `cargo_responsavel` - Job position of the owner.
* `time_responsavel` - Team of the owner.
* `cargos_vinculados` - Job positions linked to the IDP.
* `competencias_vinculadas` - Competencies linked to the IDP.
* `prazo` - Due date of the record.
* `status_pdi` - Current status of the IDP.
* `progresso_pdi` - Current progress of the IDP, as a percentage.
Initiatives, with owner, hierarchy, progress and the key result each one supports.
Table: `initiatives`
**Key Fields:**
* `id_iniciativa` - Identifier of the initiative.
* `nome_empresa` - Name of the company the record belongs to.
* `iniciativa` - Name of the initiative.
* `descricao` - Free-text description of the record.
* `nro_sub_iniciativas` - Number of sub-initiatives under the initiative.
* `id_iniciativa_pai` - Identifier of the parent initiative.
* `nome_iniciativa_pai` - Name of the parent initiative.
* `status_iniciativa` - Current status of the initiative.
* `data_inicio` - Start date of the record.
* `data_final` - Planned end date of the record.
* `situacao_iniciativa` - Current state of the initiative (for example on time or late).
* `progresso_iniciativa` - Current progress of the initiative, as a percentage.
Initiatives created inside IDPs (individual development plans).
Table: `initiatives_pdi`
**Key Fields:**
* `id_iniciativa` - Identifier of the initiative.
* `nome_empresa` - Name of the company the record belongs to.
* `iniciativa` - Name of the initiative.
* `descricao` - Free-text description of the record.
* `status_iniciativa` - Current status of the initiative.
* `data_inicio` - Start date of the record.
* `data_final` - Planned end date of the record.
* `situacao_iniciativa` - Current state of the initiative (for example on time or late).
* `data_conclusao` - Date the initiative was completed.
* `progresso_iniciativa` - Current progress of the initiative, as a percentage.
* `disponivel_avaliacao` - Whether the initiative is available for evaluation.
* `origem` - Where the record originated (for example manual creation or an integration).
Initiatives created inside 1-on-1 meetings.
Table: `initiatives_one_one`
**Key Fields:**
* `id_iniciativa` - Identifier of the initiative.
* `nome_empresa` - Name of the company the record belongs to.
* `iniciativa` - Name of the initiative.
* `status_iniciativa` - Current status of the initiative.
* `data_inicio` - Start date of the record.
* `data_final` - Planned end date of the record.
* `situacao_iniciativa` - Current state of the initiative (for example on time or late).
* `data_conclusao` - Date the initiative was completed.
* `progresso_iniciativa` - Current progress of the initiative, as a percentage.
* `disponivel_avaliacao` - Whether the initiative is available for evaluation.
* `origem` - Where the record originated (for example manual creation or an integration).
* `id_responsavel` - Identifier of the owner.
1-on-1 meetings, with participants, talking points and linked initiatives.
Table: `one_one`
**Key Fields:**
* `id_one_one` - Identifier of the 1-on-1 meeting.
* `nome_empresa` - Name of the company the record belongs to.
* `template` - Template used to create the record.
* `status_one_one` - Current status of the 1-on-1 meeting.
* `id_usuario_remetente` - Identifier of the sender.
* `nome_usuario_remetente` - Name of the user who sent the record.
* `status_remetente` - Status of the employee who requested the 1-on-1 meeting.
* `id_gestor_remetente` - Identifier of the sender's manager.
* `nome_gestor_remetente` - Name of the sender's manager.
* `data` - Date the record refers to.
* `horario` - Scheduled time of the meeting.
* `duracao` - Duration of the meeting, in minutes.
Succession mapping per job position, with current holders and mapped candidates.
Table: `succession`
**Key Fields:**
* `id_cargo` - Identifier of the job position.
* `nome_empresa` - Name of the company the record belongs to.
* `nome_cargo` - Name of the job position.
* `descricao` - Free-text description of the record.
* `dificuldade` - How hard the job position is to replace.
* `impacto` - Business impact of the job position.
* `situacao_cargo` - Current state of the job position.
* `classificacao` - Classification assigned to the record.
* `requisitos_posicao` - Requirements defined for the job position.
* `usuarios_atuais` - Employees currently holding the job position (JSON array of objects).
* `sucessao` - Succession candidates mapped for the job position (JSON array of objects).
## Engagement
Feedback exchanged between employees, with sender, recipient, question and answer.
Table: `feedbacks`
**Key Fields:**
* `id_feedback` - Identifier of the feedback.
* `acao` - Action recorded on the feedback (for example sent or requested).
* `data_feedback` - Date the feedback was registered.
* `prazo_esperado` - Date by which the feedback request is expected to be answered.
* `id_usuario_remetente` - Identifier of the sender.
* `matricula_usuario_remetente` - Employee registration number (matrícula) of the sender.
* `usuario_remetente` - Name of the user who sent the record.
* `cargo_usuario_remetente` - Job position of the sender.
* `time_usuario_remetente` - Team of the sender.
* `id_usuario_destinatario` - Identifier of the recipient.
* `matricula_usuario_destinatario` - Employee registration number (matrícula) of the recipient.
* `usuario_destinatario` - Name of the user who received the record.
Praise wall entries, with the badge and tags attached to each praise.
Table: `praises_board`
**Key Fields:**
* `id_elogio` - Identifier of the praise.
* `elogio` - Text of the praise.
* `data` - Date the record refers to.
* `hora` - Time of day the record was created.
* `id_usuario_remetente` - Identifier of the sender.
* `usuario_remetente` - Name of the user who sent the record.
* `badge` - Badge attached to the praise.
* `tags` - Tags linked to the record.
* `id_usuario_elogiado` - Identifier of the praised employee.
* `usuario_elogiado` - Name of the praised employee.
Mood thermometer entries, with the reported mood, its reason and work categories.
Table: `feelings`
**Key Fields:**
* `id_sentimento` - Identifier of the mood entry.
* `id_usuario` - Identifier of the user.
* `usuario` - Name of the user.
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
* `id_time` - Identifier of the team.
* `time` - Name of the team the employee belongs to.
* `id_gestor` - Identifier of the manager.
* `gestor` - Name of the manager.
* `id_tipo_sentimento` - Identifier of the mood type.
* `tipo_sentimento` - Type of mood reported by the employee.
* `id_motivo` - Identifier of the reason.
## Surveys
Surveys and their participation summary. Their ids drive the answer streams.
Table: `surveys`
**Key Fields:**
* `id_pesquisa` - Identifier of the survey.
* `nome_pesquisa` - Name of the survey.
* `id_tipo_pesquisa` - Identifier of the survey type.
* `tipo_pesquisa` - Type of the survey.
* `id_questionario` - Identifier of the questionnaire.
* `questionario` - Name of the questionnaire used by the survey.
* `data_inicio` - Start date of the record.
* `data_fim` - End date of the record.
* `situacao` - Current state of the record as shown in Elofy.
* `pesquisa_anonima` - Whether answers are collected anonymously.
* `numero_pendencias_enviadas` - Number of survey invitations sent.
* `numero_respondentes` - Number of employees who answered the survey.
Answers to standard surveys and polls, one row per respondent and question. Extracted per survey, in batches of survey ids.
Table: `survey_standard`
**Key Fields:**
* `id_pesquisa` - Identifier of the survey.
* `nome_pesquisa` - Name of the survey.
* `situacao_pesquisa` - Current state of the survey.
* `data_envio_pesquisa` - Date the survey was sent.
* `id_usuario` - Identifier of the user.
* `usuario` - Name of the user.
* `id_cargo` - Identifier of the job position.
* `cargo` - Name of the job position held by the employee.
* `id_time` - Identifier of the team.
* `time` - Name of the team the employee belongs to.
* `id_gestor` - Identifier of the manager.
* `nome_gestor` - Name of the manager.
Answers to pulse surveys, one row per respondent and question. Extracted per survey, in batches of survey ids.
Table: `survey_pulse`
**Key Fields:**
* `id_pesquisa` - Identifier of the survey.
* `nome_pesquisa` - Name of the survey.
* `situacao_pesquisa` - Current state of the survey.
* `data_pulso` - Date the pulse survey round refers to.
* `data_resposta` - Date the answer was submitted.
* `id_usuario` - Identifier of the user.
* `usuario` - Name of the user.
* `id_time` - Identifier of the team.
* `time` - Name of the team the employee belongs to.
* `id_gestor` - Identifier of the manager.
* `gestor` - Name of the manager.
* `id_categoria_pergunta` - Identifier of the question category.
Answers to offboarding surveys, one row per respondent and question. Extracted per survey, in batches of survey ids.
Table: `survey_dismiss`
**Key Fields:**
* `id_pesquisa` - Identifier of the survey.
* `nome_pesquisa` - Name of the survey.
* `id_publico_pesquisa` - Identifier of the survey audience.
* `id_usuario_desligado` - Identifier of the offboarded employee.
* `matricula_usuario_desligado` - Employee registration number (matrícula) of the offboarded employee.
* `usuario_desligado` - Name of the offboarded employee.
* `id_cargo_usuario_desligado` - Identifier of the offboarded employee's job position.
* `cargo_usuario_desligado` - Job position of the offboarded employee.
* `id_time_usuario_desligado` - Identifier of the offboarded employee's team.
* `time_usuario_desligado` - Team of the offboarded employee.
* `id_gestor_desligado` - Identifier of the offboarded employee's manager.
* `matricula_gestor_desligado` - Employee registration number (matrícula) of the offboarded employee's manager.
Answers to temporal surveys (follow-ups), one row per respondent and question. Extracted per survey, in batches of survey ids.
Table: `survey_temporal`
**Key Fields:**
* `id_pesquisa` - Identifier of the survey.
* `nome_pesquisa` - Name of the survey.
* `situacao_pesquisa` - Current state of the survey.
* `data_envio_pesquisa` - Date the survey was sent.
* `id_tipo_respondente` - Identifier of the respondent type.
* `tipo_respondente` - Type of the respondent in the temporal survey.
* `id_usuario_respondente` - Identifier of the respondent.
* `usuario_respondente` - Name of the respondent.
* `id_cargo_usuario_respondente` - Identifier of the respondent's job position.
* `cargo_usuario_respondente` - Job position of the respondent.
* `id_time_usuario_respondente` - Identifier of the respondent's team.
* `time_usuario_respondente` - Team of the respondent.
## Integrations
Per-record result of the HR system integration batches that feed Elofy.
Table: `integration_situation`
**Key Fields:**
* `id_lote` - Identifier of the integration batch.
* `codigomovimento` - Code of the movement processed in the integration batch.
* `codigoempresa` - Company code sent by the source HR system.
* `matricula` - Employee registration number (matrícula) of the user.
* `cpf` - CPF (Brazilian taxpayer registration) of the user.
* `email_usuario` - Email address of the user in the source HR system.
* `login` - Login used by the user to access Elofy.
* `tipousuario` - User type sent by the source HR system.
* `nomecompleto` - Full name of the employee sent by the source HR system.
* `dataadmissao` - Hiring date sent by the source HR system.
* `datadesligamento` - Termination date sent by the source HR system.
* `datanascimento` - Date of birth sent by the source HR system.
HR system integration batches, with their window and processed record count.
Table: `integration_batch`
**Key Fields:**
* `id_lote` - Identifier of the integration batch.
* `codigo_grupo_economico` - Code of the economic group in the source HR system.
* `data_inicio` - Start date of the record.
* `data_fim` - End date of the record.
* `qtd_registros_integrados` - Number of records integrated in the batch.
* `situacao_lote` - Processing state of the integration batch.