> For the complete documentation index, see [llms.txt](https://support.docstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.docstudio.com/admin-panel/users-and-user-roles/user-behaviors.md).
# User behaviors
This document explains what happens when you invite unregistered or an already registered user to your account.
{% hint style="info" %}
A corporate account administrator manages the company account in the **Admin panel**. **Corporate Account Admin** — is a user who has access to the company's account, in which a verified and active domain is registered.
{% endhint %}
### Unregistered user behavior
After you, as an Admin create an invitation, an unregistered user receives an email with a link to the registration form.
When the user opens the link, the registration form is pre-filled with the email address. It also includes the name if you provided it in the invitation. The email field cannot be edited.
After the user completes the required fields and confirms registration, the system creates a user profile, an account, and one or more mailboxes. The user then receives access rights based on the permissions you configured when sending the invitation.
### Registered User Behavior
After you create an invitation, a registered user receives an email with a link to the **Invitations** tab in their profile.
In the **Invitations** tab, the user can review all invitations and accept or decline them:
* To accept an invitation, click **Accept**. The status changes to **Accepted**.
* To decline an invitation, click **Decline**. The status changes to **Rejected**.
After the user accepts or declines your invitation, you receive a notification with their decision.
---
# 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://support.docstudio.com/admin-panel/users-and-user-roles/user-behaviors.md?ask=&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.
