Register
Tags, categories, serials, purchase and warranty details, location and condition.
Every laptop, camera and chair, and who has it
Keep a register of company equipment, know who has what, and get it back when people leave.
Each domain keeps an asset register with tags from a series (AN-0001), a category (laptop, phone, camera, mic, lens, light, furniture, licence, vehicle, other), brand, model, serial, purchase date, cost, vendor, invoice link, warranty end, location, condition, status and a photo link. Assets are issued to a team member or a named person with an expected return date; the holder confirms receipt through an emailed link with their typed name, and a return records the condition (damaged goes to repair). The history shows who had each asset and what each person holds, for exits. A4 sheets of QR labels point to /a/<tag>: the public sees the name and "belongs to" with a way to report it found or faulty, the team sees the record and checks it in or out. Maintenance and warranty dates, audits that mark each asset found, damaged or missing, and depreciation by written-down value or straight line (Income-tax block rates as defaults) give a book value on any date and per financial year. A daily 10:00 IST cron reminds holders of returns and sends one digest. CSV import and export, GET /api/v1/assets for People and exits, and webhooks.
What Assets does for you.
Tags, categories, serials, purchase and warranty details, location and condition.
Issue, acknowledge and return, with the history of who had each asset.
Printable QR labels, a scan page, audits, maintenance and depreciation.
A suggested path for Assets. What you can do depends on your access in the app.
Add them one by one or import a CSV.
Issue to a team member, who confirms receipt.
Run an audit and see the book value by category.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain keeps an asset register with tags from a series (AN-0001), a category (laptop, phone, camera, mic, lens, light, furniture, licence, vehicle, other), brand, model, serial, purchase date, cost, vendor, invoice link, warranty end, location, condition, status and a photo link. Assets are issued to a team member or a named person with an expected return date; the holder confirms receipt through an emailed link with their typed name, and a return records the condition (damaged goes to repair). The history shows who had each asset and what each person holds, for exits. A4 sheets of QR labels point to /a/<tag>: the public sees the name and "belongs to" with a way to report it found or faulty, the team sees the record and checks it in or out. Maintenance and warranty dates, audits that mark each asset found, damaged or missing, and depreciation by written-down value or straight line (Income-tax block rates as defaults) give a book value on any date and per financial year. A daily 10:00 IST cron reminds holders of returns and sends one digest. CSV import and export, GET /api/v1/assets for People and exits, and webhooks.
Products for sale belong to Store; bookable resources belong to Timeslots; buying them belongs to Purchases.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
assets.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.