Assets don't exist in isolation. They belong to people, sit in locations, and are bought from vendors.
A person is someone an asset can be assigned to. People are not the same as AssetBolt logins,, you can track a person who has never signed in.
Email is required when creating a person. Name, phone, job title, employee ID, active toggle, and notes are optional.
Employee IDs must be unique within your organization. An employee ID frees up again once the person is deleted.
You don't have to create a person ahead of time. When checking out a device, if the assignee isn't listed yet, you can create them on the spot from the assign-to field, as long as you have permission to manage people. A valid email is still required.
You don't have to create a person ahead of time. When checking out a device, if the assignee isn't listed yet, you can create them on the spot from the assign-to field, as long as you have permission to manage people. A valid email is still required.
A team groups people together. Name is required; description is optional. An email address is optional but must be a valid address if you enter one.
A person can belong to many teams. Teams matter most for digital assets, where a team can be named as the custodian.
Okta, Microsoft Entra ID, and Google Workspace connections can feed a directory group's membership straight into an AssetBolt team. Open the connection under Settings > Integrations, find the Team sync section, and link a directory group to a new or existing team. Linking requires permission to manage the organization.
Once linked:
Group members are matched to people by email and added to the team automatically. A member without a matching person is skipped until that person syncs in.
People removed from the group are removed from the team on the next sync.
Members you add to the team by hand are never touched by sync. Manually adding someone the sync already manages claims their membership as manual, so sync stops removing them.
The team page shows a badge naming the source group, and each synced member is marked "Synced." Synced members can't be removed by hand while the link is active, the group is where that has to happen.
Sync runs on the connection's regular schedule and on demand from "Sync now." If the linked group is deleted upstream, the link shows as broken and every synced membership converts to manual rather than disappearing. Unlinking a group at any time keeps the team and its members; synced members simply become manual and stop following the group.
A directory group can only feed one team, and a team can only be fed by one group.
A location is where something is. Name is required; everything else is optional.
Location types: Office (the default), Warehouse, Data center, Remote, Home office, Storage, Other.
Locations nest. Each location can have a parent, so a rack sits inside a room, inside a floor, inside a building. The locations page shows this as a tree.
A location can be marked virtual,, useful for "in transit" or "with IT" placeholders that don't correspond to a physical address.
Location tracking on assets requires a Pro plan or higher.
A vendor is who you buy from. Name is required. Email must be a valid address or left blank. Rating accepts 0 to 5; reliability score accepts 0 to 100. Everything else is optional.
Vendors can be attached to maintenance records, so you can see who repaired what.
Vendor statuses include Active, which is the default.
A manufacturer made the thing. Only Name is required, plus an active toggle; contact, support, address, and contract fields are all optional.
A model groups assets by manufacturer and category,, "MacBook Pro 14-inch, M4". Only Name is required. Devices, accessories, and consumables can all share a model.
You don't need to create manufacturers, models, or categories in advance. All three can be created inline while editing a device.
