> For the complete documentation index, see [llms.txt](https://help.kenyalaw.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.kenyalaw.org/your-account/create-an-account.md).

# Create an account

Create an account on Kenya Law to save documents, set alerts, and follow topics.

Creating an account helps you keep track of your research and return to important documents quickly.

## Create your account

1. Click [**Log In**](https://new.kenyalaw.org/accounts/login/) at the top of the site.
2. Click **Don't have an account? Sign up**.
3. Enter your details and choose a secure password.
4. Click **Sign up** to create your account.

## If you cannot create an account

If you do not see an option to log in or create an account, account access may be managed differently for your site. Contact your site administrator or support team for access.


---

# 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://help.kenyalaw.org/your-account/create-an-account.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.