> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/applicant-help-guides/accounts/applicant-registration.md).

# Applicant Registration

{% stepper %}
{% step %}

### Visit the sign up page

![](/files/1fc1ac72c5d30dbd63a0ebb29e07302abe35d9f2)
{% endstep %}

{% step %}

### Enter email and password, agree to terms, and sign up

Type in your email and password, review and agree to terms and conditions, click **Sign up.**

![](/files/8644dd9fda5f3366701bb0e82dad9235e18544db)
{% endstep %}

{% step %}

### Select individual or company, enter details, and register

Select to apply as an individual or company, enter details, then click **Register.**

![](/files/9689d14dee0ac2fff276fc52e36541ee546b5812)

![](/files/7fb736369358a33cf9bc33c657100aa7b9c68a9b)
{% endstep %}
{% endstepper %}

## Individuals vs Companies

Overview: It is common for **individuals** to apply for grants on behalf of **companies** (also referred to as organisations). For example, an individual (such as a Sports Coordinator for a University) might apply for and manage grants on behalf of a number of different sports teams within the University.

To enable the Sports Coordinator (an individual) to apply for different sport teams, they can use the organisation function (also referred to as a company) to create separate profiles per team. Even though a sports team isn’t always a “company” or an “organisation”, this function is the best way to manage separate entities (such as clubs, departments, groups, and teams). If the individual didn’t use this function for each sports team, they would have to create a separate login per team with a unique email address. This isn’t practical and makes managing grants more difficult.

***

## What’s next?

* You can search and [apply for Grants.](broken://pages/e706ce22742defe89b4de343456de6f745ce5c12)
* Update your [profile](broken://pages/d9d961c7750895211d10ddd1771409c879899c73) at any time.
* Create and manage [organisations](broken://pages/38421cb8ef31a07b7208aac533e915c0d2a8e829).

### Related articles

* [Apply for a Grant](broken://pages/879e25e1c244d550d7bd0f9dd58ad23fe77f9ff1)
* [Invite a New Applicant](broken://pages/6d1da1f2dfce488269a3355006007a3a271b9d6e)
* [Profile Management](broken://pages/adc05871686582fab96e897cec9b6fd17790a034)
* [Information Requests](broken://pages/8d8518f8d1792e0b361acd7bcee65124819b410d)
* [Applicant Milestones](broken://pages/1a54fd7cbf9c36e39a044ea5d6579ed27a2691cd)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.tahua.io/knowledge-base/applicant-help-guides/accounts/applicant-registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.