---
title: "What's next? Essential info"
canonical: "https://support.appfire.com/space/FD/2832761420/What's%20next%3F%20Essential%20info"
format: markdown
---
> Macro (aura-html)

The **What’s next** screen provides more context on the transition from setup to active usage.

![The what's next page summarizing the essential setup.](media://d90b2e96-3fa0-4976-90ea-226ff1c0f546)

### Post-setup activity

While you finalize your initial configurations, Flow performs several automated background tasks to ensure data integrity. The system actively de-duplicates commits and user identities, cleanses raw engineering activity, and populates your first set of metrics dashboards. This backend processing transforms fragmented Git data into a coherent narrative of your team’s development lifecycle.

### Identifying early adopters

Once the foundation is laid, the platform is ready for its first wave of active users. The ideal initial audience includes:

- **Team Leads:** To begin identifying bottlenecks and coaching opportunities.
- **Pilot Teams:** To test the platform’s utility and accuracy before a full-scale organizational rollout.
- **Core Engineers:** To provide feedback on Git usage patterns and ensure the data reflects their daily workflows accurately.

### Success criteria for the next phase

You have successfully completed the Essential Setup and are ready for the advanced Insights Configuration when the following benchmarks are met:

- You have a firm grasp of Flow’s unique terminology and hierarchical structure.
- Git data is flowing into the platform without errors, and initial metrics are visible in your reports.
- Foundational settings—specifically user merges, default domains, and merge strategies—have been established.
- You have identified enough initial value in the data to confidently invite more stakeholders into the platform.

### A note on identity and security

It is normal to encounter unfamiliar names or email addresses during the initial import. Because Flow pulls all identities associated with your Git history and third-party integrations, the list of users may appear cluttered at first. 

The platform’s security and accuracy will continue to improve as you refine your context—mapping teams, defining domains, and merging aliases into "Apex" profiles.