> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/lidarmill-cloud/login-register/sub-accounts.md).
# User management
When you [register](https://docs.phoenixlidar.com/lidarmill-cloud/login-register) a new account, it is required to fill in details about your company. As a result, your account will belong to that company and will be marked as an administrator account.
### Inviting new company members
To invite a new company member, go to the "Users" page and open the "General" tab.
There you will be able to find the buttons for generating the invites for a "Customer" and an "Employee".
After clicking on either of them, you will be prompted to type the user email on which an invitation will be sent.
Please see the ["Permissions table"](https://docs.phoenixlidar.com/lidarmill/sub-accounts#permissions-table) for understanding the differences between the "Employee" and "Customer".
### Registering the new account using an invitation
### Sharing the projects with your customer
After the "Customer" was invited and registered his LiDARMill account he will see none of your companies projects before you explicitly share some.
For sharing the particular project with one of your customers go to the "Shared projects" page on LiDARMill and click on the customer you want to share the project with.
Click on the "Add permission to read selected projects" button and select the one or multiple projects you want to share with and confirm your choice.
After the project is shared it will be listed in the list and you will be able to disable the sharing at any moment.
When the "Customer" was granted to read some projects they will be listed in his LiDARMill account.
The "Customer" will be able to see all information about the shared project and download the data from it but won't be able to upload the data, start any kind of processing, edit, or remove the project.
### Permissions table
The "Customer" can see and download data only from the projects what were shared with him.
| Action/Role | Administrator | Employee | Customer |
| ---------------------------------------------- | :------------------: | :------------------: | :-----------------------------------------------------------------------------------------------------------------------------------: |
| Invite new "Employe" | :white\_check\_mark: | :x: | :x: |
| Invite new "Customer" | :white\_check\_mark: | :white\_check\_mark: | :x: |
| Manage the subscriptions | :white\_check\_mark: | :x: | :x: |
| Update companies details (name, URL, etc..) | :white\_check\_mark: | :x: | :x: |
| Access to projects which belong to the company | :white\_check\_mark: | :white\_check\_mark: |
✅
only for projects which were shared
|
| Process the data | :white\_check\_mark: | :white\_check\_mark: | :x: |
| Upload the data | :white\_check\_mark: | :white\_check\_mark: | :x: |
| Download the data | :white\_check\_mark: | :white\_check\_mark: |
✅
only for projects which were shared
|
###
---
# 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://docs.phoenixlidar.com/lidarmill-cloud/login-register/sub-accounts.md?ask=&goal=
```
`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.