NinjAsset

Lazy cat OIDC login has been integrated. ##Functional characteristics - Asset inventory management: Support `STOCK`,`ASSIGNED`,`MAINTENANCE`,`ARCHIVED` life cycles and asset details. - Site and map: Manage office, data center and asset coordinates, and use the map to view asset distribution. - Handover confirmation: Sign in/return confirmation is completed through magic links, and printable PDF receipts and signature file upload are supported. - ITAM Catalog: Maintains vendor, supplier, classification and classification custom fields. - Media and QR codes: asset pictures, avatars, manufacturer/supplier pictures, asset QR codes and label printing. - Data quality and alarms: Calculate asset health rules and support reporting, notification bells and alarm ignore. - Batch allocation: Batch check-out/return from the asset list, supporting direct allocation or verification handover. - Audit history: Record administrator actions, user history and asset transactions. - API automation: Administrators can create a Bearer API Key for scripts to call the management interface. - Webhook integration: Supports event notification targets such as Slack, Discord, and Telegram. - Import and export: Migrate asset, site, user and directory data via CSV/XLSX/JSON, supporting dry-run and asynchronous tasks. - AI Assistant: Administrator RAG Assistant based on Qdrant, Embedding and Grok/xAI has been connected, and can be activated by filling in the model and key through the configuration wizard. ###Daily usage 1. . 'Overview' is used to see the total asset amount, allocation, site and user size;'Reports' is used to view data quality issues; and 'Users' is used to manage users. 2. `Assets` is used to maintain asset master data, pictures, QR codes, allocation status and location;`Sites` is used to maintain site and map coordinates; and `Categories / Manufacturers / Vendors` is used to maintain the ITAM catalog. 3. `Import / Export` is suitable for batch migration and daily batch processing: download the template before import, do `Dry-run` first when importing, and then `Commit` after confirming that the mapping and verification are correct. 4. `API keys` are used to generate script access tokens;`Integration` is used to configure notification targets such as Slack, Discord, and Telegram; and `AI Assistant` is used to ask questions about functions, processes, configuration, and API-related issues. 5. All image uploads, imported file selections, and QR code PNG downloads go through the lazy cat file process after injection by default; if you use a local device, you can also directly choose to open or save locally. ###Optional Configuration 1. `Grok API Key`: The required key for the AI assistant to call xAI/Grok. When you do not fill in, the AI page can open, but you cannot answer normally. 2. `Grok Model`: The model name in the configuration wizard. The default value is `grok-4.3`. When you need to switch models, you can just change it here directly without changing the image. 3. `AI HTTPS Proxy` or `AI Universal Proxy`: If you need to use AI functions, please configure them accordingly, and it needs to be used in conjunction with Piggy Page. 5. `AI direct connection whitelist`: By default,`127.0.0.1,localhost, qdrant, backend, frontend, postgresql, redis, aiagent` is included, and usually does not need to be changed; only if you adjust the internal service name or route, you need to modify it. 6. SMTP: If you need outgoing capabilities such as email verification and password reset, you need to supplement SMTP-related configurations. Please go to the application details-environment variables to modify it, see the attached figure. 7. Webhook: If you need to actually send Slack, Discord, and Telegram events, in addition to front-end page configuration, you also need to ensure that the corresponding capabilities are enabled when publishing on the backend. Please go to the application details-environment variables to modify it, see the attached figure.