# Standardize and automate Developer Onboarding
To configure your Cortex workspace for successful Developer Onboarding, we recommend the following actions:
* **Connect Data**: [Ingest data and ensure ownership](#step-1-ingest-data-and-solve-ownership) is assigned to your entities
* **Streamline**: Automate common onboarding processes via [Workflows](#step-2-automate-onboarding-processes-via-workflows), have new developers configure [Cortex MCP](#step-3-configure-cortex-mcp) to get quick answers about your workspace and environment, and view centralized daily tasks on the [engineering homepage](/solutions/dev-onboarding/in-action.md#review-prioritize-and-complete-tasks)
* **Improve**: Managers can review [Eng Intelligence metrics](#step-4-review-eng-intelligence-metrics) and take action when issues in the onboarding process are surfaced
## Use Cortex features to successfully onboard developers
Expand the tiles below to learn about configuring Cortex features to onboard new developers.
Step 1: Ingest data and solve ownership🔌
{% hint style="success" %}
**Action Items:**
* [**Import your data**](/ingesting-data-into-cortex/overview.md)
* [**Ensure ownership is set**](/ingesting-data-into-cortex/entities-overview/entities/ownership.md)
* [**Configure integrations**](/ingesting-data-into-cortex/integrations.md)
{% endhint %}
Before getting started on any use case, it is crucial to import your services, resources, infrastructure, and other entities, and to have clear visibility into the ownership of your entities.
Connecting your entities to Cortex establishes a single source of truth across your engineering organization. It enables the ability to track progress via Scorecards, automate Workflows, and gain insights from Eng Intelligence. It also gives new engineers a clear view of the systems they need to interact with.
Setting ownership of entities ensures that every service and system is clearly linked to accountable teams or individuals, enabling faster incident response, reducing handoff friction, and making it possible to enforce standards consistently.
#### Relevant integrations
Before you focus on Developer Onboarding, Cortex recommends integrating with your essential tools so you can establish best practices before bringing on new team members:
* **Version control**: [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops.md), [Bitbucket](/ingesting-data-into-cortex/integrations/bitbucket.md), [GitHub](/ingesting-data-into-cortex/integrations/github.md), [GitLab](/ingesting-data-into-cortex/integrations/gitlab.md)
* Enforce best practices like peer reviews, CI/CD pipelines, and versioning
* **Teams/ownership:** [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops.md), [BambooHR](/ingesting-data-into-cortex/integrations/bamboohr.md), [Entra ID](/ingesting-data-into-cortex/integrations/entraid.md) (formerly Azure Active Directory), [GitHub](/ingesting-data-into-cortex/integrations/github.md), [GitLab](/ingesting-data-into-cortex/integrations/gitlab.md), [Google](/ingesting-data-into-cortex/integrations/google.md), [Okta](/ingesting-data-into-cortex/integrations/okta.md), [Opsgenie](/ingesting-data-into-cortex/integrations/opsgenie.md), [ServiceNow](/ingesting-data-into-cortex/integrations/servicenow.md), and [Workday](/ingesting-data-into-cortex/integrations/workday.md).
* Ensure entities have owners and foster a culture of accountability
* **On-call**: [PagerDuty](/ingesting-data-into-cortex/integrations/pagerduty.md), [Opsgenie](/ingesting-data-into-cortex/integrations/opsgenie.md), [Splunk On-Call](/ingesting-data-into-cortex/integrations/splunk-oncall.md) (formerly VictorOps), [xMatters](/ingesting-data-into-cortex/integrations/xmatters.md)
* Track on-call responsibilities to confirm that support teams are always assigned
* **Project management**: [GitHub](/ingesting-data-into-cortex/integrations/github.md), [Jira](/ingesting-data-into-cortex/integrations/jira.md), [Azure DevOps](/ingesting-data-into-cortex/integrations/azuredevops.md), [ClickUp](/ingesting-data-into-cortex/integrations/clickup.md)
* Track incidents, bugs, and compliance issues
* **Communication**: [Slack](/ingesting-data-into-cortex/integrations/slack.md), [Microsoft Teams](/ingesting-data-into-cortex/integrations/microsoftteams.md)
* Having communication tools connected is crucial for ensuring new developers know which channels to communicate in when they have questions about specific entities, and ensuring developers receive [notifications](/configure/settings/notifications.md) from Cortex
* **Code quality and security**: [Checkmarx](/ingesting-data-into-cortex/integrations/checkmarx.md), [Codecov](/ingesting-data-into-cortex/integrations/codecov.md), [Mend](/ingesting-data-into-cortex/integrations/mend.md), [Snyk](/ingesting-data-into-cortex/integrations/snyk.md), [SonarQube](/ingesting-data-into-cortex/integrations/sonarqube.md), [Veracode](/ingesting-data-into-cortex/integrations/veracode.md), [Wiz](/ingesting-data-into-cortex/integrations/wiz.md)
* Enforce code coverage, vulnerability scanning, and other quality measures
Cortex also recommends [linking to runbooks and documentation](/ingesting-data-into-cortex/entities-overview/entities/external-docs.md) for your entities, ensuring your users have access to critical information.
With your data in Cortex, you have a jumping-off point to configure your workspace for a streamlined onboarding process for new engineers.
Step 2: Automate onboarding processes via Workflows⚙️
{% hint style="success" %}
**Action item:** [**Configure Workflows**](/streamline/workflows.md)
{% endhint %}
You can use Workflows to streamline and standardize onboarding processes, reducing the manual effort required to get started.
#### Workflows to streamline onboarding processes
* Configure Workflows to provision access to tools (such as [GitHub, PagerDuty, Jira,](broken://spaces/JW7pYRxS4dHS3Hv6wxve/pages/tTc0xO4VesngCGWvcSuJ) and [GitHub Copilot](broken://spaces/JW7pYRxS4dHS3Hv6wxve/pages/dyOiPs79oZDoGINSsawI)) and [set up a new test environment](broken://spaces/JW7pYRxS4dHS3Hv6wxve/pages/EwASISKk4rRWFxw4xq5H) for an engineer.
#### Workflows to establish adherence to best practices
* When Scaffolding new services, you can use templates to ensure that every new service starts with baseline standards, helping your new developers be successful from day one.
* See the documentation on [registering a Scaffolder template](/streamline/workflows/scaffolder.md) and [configuring a Scaffolder block](/streamline/workflows/blocks.md#scaffolder).
Step 3: Configure Cortex MCP🤖
{% hint style="success" %}
**Action Item for new developers:** [**Configure Cortex MCP**](/get-started/mcp.md)
{% endhint %}
[Cortex MCP](/get-started/mcp.md) reduces onboarding friction by meeting new engineers where they work (their IDE) and letting them self-serve Cortex context in natural language.
Ask questions like "Who is on call for backend-server?" or "Give me all the details for parser-service." MCP fetches the data in real time from Cortex's API, ensuring accurate and up-to-date information about service health, ownership, and operational readiness.
Step 4: Review Eng Intelligence metrics📈
{% hint style="success" %}
**Action Item for managers:** [**Review Eng Intelligence metrics**](/improve/eng-intelligence.md)
{% endhint %}
Managers can use Eng Intelligence features — the [DORA dashboard](/improve/eng-intelligence/dashboards/dora-dashboard.md), [Velocity Dashboard](/improve/eng-intelligence/dashboards/velocity-dashboard.md), and [Metrics Explorer](/improve/eng-intelligence/metrics-explorer.md) — to surface and track key engineering metrics related to developer productivity.
Review trends in areas such as deployment frequency, review latency, and other indicators that are important to your organization. This helps you identify areas where your new developers and their teams might need additional support.
## Developer Onboarding in action
Learn about following Developer Onboarding processes in Cortex in [Developer Onboarding in action](/solutions/dev-onboarding/in-action.md).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.cortex.io/solutions/dev-onboarding/configure.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.