# Basic Details

Provide the essential information required to create the system. These details help accurately categorize and describe the system for future identification and use.

Fields to collect:

* **System Logo**\
  Builders are required to upload a system image to visually represent the system. The image must be less than 5MB in size and must be in one of the following formats: JPEG, JPG, or PNG.
* **System Name**\
  A unique and clear name for the system. This is how it will be identified across workflows and configurations.
* **System Documentation Link**\
  A URL pointing to the API documentation or user guide for the system. Helps system users understand how to use or integrate with the system.
* **System Type**\
  Choose from one of the following predefined types:

  * ERP: For enterprise resource planning systems like SAP, NetSuite, or Oracle ERP.
  * CRM: For customer relationship management systems like Salesforce or HubSpot.
  * Files: For file storage and transfer systems like Google Drive, Dropbox, or SFTP.
  * ECommerce: For online commerce platforms like Shopify, Magento, or WooCommerce.
  * Others: For any system that doesn’t fit the above categories.<br>

  Selecting the right type helps in organizing systems, filtering them, and possibly applying pre-configured defaults or behaviors based on type.
* **Description**\
  An optional text field to describe the purpose or behavior of the system for better clarity.


---

# Agent Instructions: 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:

```
GET https://docs.dckapintegrator.com/project-manager/systems-builder/new-private-system/basic-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.