> For the complete documentation index, see [llms.txt](https://pikasso-1.gitbook.io/pikasso/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pikasso-1.gitbook.io/pikasso/our-product/dashboard/user-management.md).

# User Management

* Pikasso will have the following role and permission:
  * **Creator:** It's a normal user, so they can use Pikasso for creating NFT, Collection and selling or buying in Pikasso CEX. They also can deposit and manage their NFT within Pikasso or they can withdraw their NFT to their Web3 wallet. They can update the collection in public or private mode.
  * **Business User:** This account needs to request Pikasso Admin upgrade to the Pikasso business plan, so they have unlimited access. They can CRUD single or multiple projects, adding single or multiple collections to the project. They can update the project and collection in a public or private mode.
  * **Publisher**: Let publishers embed a Collection or an NFT of the Collection so they can refer and receive bonus from Pikasso.
* Allow user to view their profile, on this page users can:
  * Update user profile
    * User name 
    * Avatar
    * Wallet Address 
    * Linked social channels (Twitter, Facebook…)


---

# 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://pikasso-1.gitbook.io/pikasso/our-product/dashboard/user-management.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.