> For the complete documentation index, see [llms.txt](https://docs.mulearn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mulearn.org/how-to-use-the-platform/company/getting-started/new-user.md).

# New User

#### Purpose

Guide new users through creating a company account, completing the company profile, and accessing the Company Dashboard.

#### Page Overview

New company registration begins with creating a μLearn account, followed by selecting the **Company** role and completing a four-step company profile. Once registration is complete, you will be redirected to the Company Dashboard, where your company profile enters **Verification Pending** status.

#### Features/Sections

**Account Registration**

Create your μLearn account using:

* Full Name **(Mandatory)**
* Email Address **(Mandatory)**
* Password **(Mandatory)**
* Confirm Password **(Mandatory)**

You can also create an account using **Sign up with Google**.

**Role Selection**

Choose **Company** as your role during onboarding to register your organization on μLearn.

**Company Profile**

Complete the following four sections of your company profile.

**1. Basic Info**

| Field           | Requirement |
| --------------- | ----------- |
| Company Name    | Mandatory   |
| Logo URL        | Optional    |
| Description     | Mandatory   |
| Short Pitch     | Optional    |
| Industry Sector | Optional    |
| Company Size    | Optional    |

**2. Contact**

| Field         | Requirement |
| ------------- | ----------- |
| Contact Email | Optional    |
| Website       | Optional    |
| LinkedIn      | Optional    |

**3. Location**

| Field    | Requirement |
| -------- | ----------- |
| Location | Optional    |
| Country  | Optional    |
| State    | Optional    |
| District | Optional    |

**4. Legal Info**

| Field               | Requirement |
| ------------------- | ----------- |
| Legal Name          | Optional    |
| Registration Number | Optional    |
| Tax ID / GSTIN      | Optional    |
| Founded Year        | Optional    |
| Remote Policy       | Optional    |
| Culture Text        | Optional    |

#### Available Actions

* Register a new μLearn account.
* Sign up using Google.
* Select the Company role.
* Complete your company profile.
* Submit your registration.
* Access the Company Dashboard.

#### Step-by-Step Workflow

1. Create a new μLearn account using your email address and password, or choose **Sign up with Google**.
2. Select **Company** as your role.
3. Complete the company profile by providing the required information across the four onboarding steps.
4. Click **Complete Registration** to submit your profile.
5. You will be redirected to the Company Dashboard, where your company profile will display a **Verification Pending** status until it has been reviewed.

#### Notes

* Only the mandatory fields are required to complete registration.
* Optional fields can be added during onboarding to provide more information about your organization.
* Company-specific management features remain unavailable until your company has been verified.

#### Related Pages

* [Company Verification](/how-to-use-the-platform/company/company-verification.md)
* [Existing User](/how-to-use-the-platform/company/getting-started/existing-user.md)
* [Dashboard ](/how-to-use-the-platform/company/dashboard.md)


---

# 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.mulearn.org/how-to-use-the-platform/company/getting-started/new-user.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.