Create an Asset Workspace and its fields

Understand the outcome

Design the workspace around the decisions people need to make.

Assets lets you build the equipment registers your department actually keeps — apparatus, SCBA, medical inventory, turnout gear — as custom workspaces with 19 field types. Find records by barcode, get reminders before items expire, schedule recurring maintenance, and keep files, history, and checklist alerts on each record. The older category and location inventory has been removed.

Before you begin

Make the decision before changing the screen. Record the current configuration when the department already uses this feature, and use a test record or test account when the change can affect active members.

• Choose one kind of equipment and an owner.
• Pick a unique identifier or barcode.
• List required fields and expiration dates.

Where to work and what access you need

Start from the portal destination named in the procedure. Administrators normally need permission to view Assets plus the specific create, edit, manage, approve, report, or all-record action used by the task. Visibility alone does not grant management access.

• Asset Workspaces/modules/assets/tables
• New workspace/modules/assets/tables/new
• Workspace records/modules/assets/tables/:id
• Configure workspace/modules/assets/tables/:id/configure
• Record profile/modules/assets/tables/:id/records/:rowId
• Due Work/modules/assets/due-work
• Settings/modules/assets/settings

Required foundation

• Core must be enabled and correctly configured before this workflow can operate reliably.

If your department uses custom roles, test the procedure with that role—not only with a full administrator account. This confirms the people responsible for daily operations can complete the workflow without receiving unrelated access.

Complete the task

1. Step 1Create the workspace

   Open Asset Workspaces and start from a template or scratch.

2. Step 2Add fields

   Choose from 19 types, including expiration, barcode, personnel, station, and apparatus.

3. Step 3Set rules

   Mark essential fields required.

4. Step 4Set icon and color

   Make it easy to recognize.

5. Step 5Set permissions

   Separate viewing, editing, and configuration.

6. Step 6Add test records

   Check search, barcode lookup, and history.

Operational safeguards

Apply these module-level controls while completing the procedure. They prevent a technically saved configuration from becoming an operational or access problem later.

• Control point
  Start with one workspace and name an owner for its data.
• Control point
  Use a stable identifier or barcode for each record.
• Control point
  Keep station and apparatus lists current under Settings → General.
• Control point
  Set required fields and expiration thresholds before importing.
• Control point
  Test permissions with a normal member role.
• Control point
  Use Checklists, not Assets, for inspections.

Verify the result

Do not consider the setup complete merely because the save action succeeded. Confirm the behavior from the user-facing or operational view, then retain evidence of the test when department policy requires it.

• Required fields are enforced.
• Barcode lookup finds the record.
• Normal users can’t change the structure.

If any verification fails, return to the source configuration and correct it there. Do not edit a report or downstream record to conceal an incorrect setup.

Troubleshooting

Station field is empty

Add stations under Settings → General.

Users see too much

Review role permissions.

Wrong field type

Fix it before importing.

Related Assets capabilities

This task sits inside a larger module workflow. These related capabilities may affect the result or provide the next administrative step:

• Custom workspaces with their own fields, icon, and color
• 19 field types, including expiration, barcode, currency, personnel, station, and apparatus
• Rear-camera barcode scanning with manual fallback, plus USB scanners
• Expiration reminders to roles and members with priority, email, and custom messages
• Recurring maintenance every N days, weeks, or months, with backdated completions and notes
• Due Work list covering the next 60 days across workspaces
• Record profiles with details, attachments, assignment, service, checklist alerts, and field history
• CSV import and export, plus bulk assign, status, retire, and delete

Use the module hub to open the dedicated procedure associated with any capability listed here.

Connected modules and downstream effects

A change here can alter what members see, what data appears in reports, or how another module completes its workflow. Review the connected areas below before making a department-wide change.

• ChecklistsApparatus, SCBA, and PPE checks with schedules and failed-item alerts.
• QuartermasterUniform and gear stock by size, role eligibility, requests, and issued gear.

After deployment, test one complete workflow from the originating module through every connected destination your department uses. Document the final configuration so another administrator can audit or reproduce it later.

Continue in Assets

Return to the Assets module guide for connected workflows, dependencies, portal destinations, and additional procedures.