> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/getting-started/first-steps-in-the-portal.md).

# First steps in the portal

Accept the invitation, set a password, configure the first application URL.

Two setup tasks, done once during onboarding, in order. Accept the portal invitation and set a password, then configure at least one application URL so Userlane knows which domains to activate on. Everything else in the portal depends on these being complete.

{% columns %}
{% column %}
{% content-ref url="/pages/T6JBjNnsSjhJFPji2nUG" %}
[Set up the account](/getting-started/first-steps-in-the-portal/set-up-the-account.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
{% content-ref url="/pages/fsN54CJn1Adx0IhuudPQ" %}
[Set up the application URL](/getting-started/first-steps-in-the-portal/set-up-the-application-url.md)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
**Looking for something else?**

Try [A tour of the Userlane portal](/getting-started/a-tour-of-the-userlane-portal.md), [Rollout](/deployment/rollout.md), or [Portal authentication](/administration/sign-in-and-permissions/portal-authentication.md).
{% endhint %}


---

# 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.userlane.com/getting-started/first-steps-in-the-portal.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.