The Objects table is the list view for everything your crews captured. Use it when you need search, filters, and paging more than a map pin. The map answers where; this table answers which record.

Which columns and fields you see come from your organization's configuration. See Why your screens may not match this guide.

If you cannot see it, your role may not include it. Ask whoever manages your organization rather than assuming something is broken.

From this list you can also Create (then Add one and pick a template), Export results as a CSV, and filter by Time or Type.

Narrow the list before you hunt by eye:

Clicking the row highlights it and does not open it. Open the object from the view control on its row instead. That is the usual stumble on this screen.

Filters, sorting, and paging stay in the page address, so you can bookmark a filtered view or send it to a colleague and it opens the same way for them.

When you open one, you get the object's type, when it was created and by whom, and when it was last changed. Below that are its attributes, images, and related connections (for example spans on a pole), as your configuration defines them.

A newly placed object that nobody has filled in yet can look almost empty. That usually means no captured data yet, not a lost record.

The job on the object is often an ID, not a clickable name. Copy that reference and match it in your jobs list when you need the job. It looks terse on purpose; nothing is missing from the link.

An object shows either an archive or an unarchive control, never both.

Archiving is reversible. It sets the object's recorded values aside rather than destroying them. After you archive, you leave the object and return to where you came from, which is easy to read as something having gone wrong. It has not.

An archived object says so when you open it, tells you when it was archived, and offers to restore it. While it is archived, field values stay hidden until you unarchive. Unarchive brings the most recently recorded values back.