> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/ursa/ursa-account-builder.md).
# Ursa account builder
#### 
[Visit Account Builder in the app](https://assetpanda.app/settings/account-builder)
When you enable UrsaAI in your organization, the Account Builder provides a specialized Ursa experience that helps you set up your Asset Panda Pro account by generating a complete organizational structure based on a description of your business.
## Information to provide
When you describe your business, Ursa creates the objects needed to support the business structure. Provide as much information as possible to ensure the appropriate structure is generated.
Be as specific as possible about the following elements:
* **Your industry or type of business**\
Mentioning your industry helps Ursa suggest relevant collections and fields. "Construction company" will produce different results than "Hospital".
* **Categories of assets, items, or resources** \
The more detail you provide about the objects you manage, the more tailored the result will be.
* **Key workflows and processes**\
Tell Ursa how you use your assets. For example: "Employees check out laptops and return them when they leave the company."
* **Team or department structure**\
Mention departments or roles that need access to the system, so Ursa can suggest appropriate organizational groupings.
{% hint style="info" %}
For best results, give a high-level description first and then add details in follow-up messages to refine the structure.
{% endhint %}
### **Example prompt**
> *We're a mid-sized IT services company. We need to track laptops, desktops, monitors, and mobile devices. Each asset should have a serial number, purchase date, warranty expiration, assigned employee, department, location, and condition status. We also manage a fleet of 20 service vehicles.*
***
## Generated objects
When you describe your business to Ursa, it can generate the following:
* **Accounts**: Top-level organizational containers for your data
* **Modules**: Groups of related collections within an account
* **Collections**: Tables that hold your records (for example, IT Assets, Vehicles, and People)
* **Fields**: The columns within each collection that define the data you track (for example, Serial Number, Purchase Date, and Assigned To)
* **Categories**: Predefined groups for organizing records within a collection (for example, Laptops, Desktops, and Monitors within an IT Assets collection)
***
## Use the Account Builder
1. In the navigation pane, select 
**Settings** > **Account Builder**. The Ursa pane is displayed in Account Builder mode.
{% hint style="info" %}
Account Builder is only available from this navigation. It is not available from the main Ursa chat interface.
{% endhint %}
2. **Define your business**\
In the chat input, describe your business and what you want to track. See [Information to provide](#information-to-provide). \
\
Ursa generates the account structure, showing you progress as it works. Once complete, it displays the proposed accounts, modules, collections and fields, and categories within each collection.
3. **Refine or regenerate**\
Review the structure to determine if it matches your needs. If it does not meet your needs, perform one of the following tasks:
* **Refine**: In the chat input, tell Ursa what to change. For example: "Add a Warranty Provider field to the IT Assets collection" or "Create a separate collection for Software Licenses".
* **Regenerate**: Click **Restart** to provide a new or updated business description and Ursa will generate a new structure.
4. **Modify the generated objects**
* To edit the name or description of an account or module, click **Edit** :pencil: for the object, update the listed information, and then click **Save**.
* To edit the name of a collection, click **Edit name** next to the collection, enter the new name, and then click **Save**.
* To review the fields for a module:
1. Click the linked module name. The fields for each collection in the module are displayed.
2. To edit a field's settings, click **Edit** in the field row, adjust the settings, then click **Save**.
3. To remove a field from the collection, click **Remove** in the field row.
4. To edit the generated categories:
1. Under **Categories**, select check boxes to determine the fields that will be included for each category name.
2. To edit a category name, click  for the category and select **Edit**. Enter the new name and click **Save**.
3. To remove a category, click  for the category and select **Delete**.
* To add fields or categories, click **Add field** or **Add Category** and specify the required information.
5. When the structure meets your business needs, click **Back** to return to the account builder view and then click **Done**. Ursa creates the account and suggested resources, then prompts you to view the new collection. Click **Yes** to view the collection.
---
# 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://prohelp.assetpanda.com/ursa/ursa-account-builder.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.