LBC Fleet · company administration

Configure the company. Verify what changed.

Update company identity, contacts, notifications, and feature controls without confusing company settings with app-wide or integration settings.

1 Open Company Info

Open Setup → Company Info, then select the intended company. Confirm the company name before choosing Update.

Fictional LBC Fleet Setup menu expanded with Company Info visible.Open full-size screenshot ↗
Fictional Sonoran Transit Demo workspace.

2 Review identity and contacts

Check carrier name, USDOT number, address, timezone, and primary and fleet contact details. For a DOT-regulated company, reconcile carrier identity against the organization’s authoritative record before saving.

Fictional Update Company form showing company identity and contact fields.Open full-size screenshot ↗
Use fictional data for training and publication screenshots.

3 Change only the intended features

Review carrier type, scheduling, HR, fleet management, HOS, recruiting, incident review, maintenance, and custom-field controls. Treat each toggle as behavior—not decoration. If its operational effect is unclear, leave it unchanged and ask the account owner.

Fictional LBC Fleet company form showing carrier and feature settings.Open full-size screenshot ↗
Labels and availability can vary by account permissions and enabled modules.

4 Keep notification recipients separate

Use Manage Emails for report and alert recipients. Confirm the recipient, notification type, and business purpose. Do not use a shared or external address unless the company authorizes it.

Different surface, different effect Company Info changes the company record. Manage Emails changes who receives selected notifications. Global Settings affects the broader application and is not part of this guide.

5 Save, reopen, and verify

Save once, reopen the same company, and verify the exact fields you intended to change. Confirm the expected menu or workflow behavior, then record who changed it and when. If the saved value or resulting behavior differs, restore the prior value and investigate.

Branding note A logo upload can save successfully without appearing in the current app header or generated work-order PDF. Do not promise either placement until that rendering path is separately verified.

Open printable checklist