Best Practices & Common Issues
Last updated: May 8, 2026
Best Practices
Plan your UAG structure first: Create and organize your User Access Groups with appropriate tags and features before inviting users
Use descriptive UAG names: Name groups clearly (e.g., "Europe Operations Team" instead of "Group1") so they're easy to identify. Want to make your life easier? Maintain consistency across your organization!
Example:
QA_Temperature_Release,US_West_Operations
Start with fewer, broader groups: Begin with regional or functional groups before creating highly specific ones
Review Admin vs Member differences: Remember Admins see all data regardless of tags, but feature access applies equally to all roles
Document your UAG strategy: Keep notes about which UAGs, tags, and features should be assigned for different job roles
π§ Feature toggle best practices:
Enable features progressively: Start with essential features enabled, add advanced features as users become familiar with the platform
Match features to user needs: Don't enable features users won't use - it simplifies their interface and reduces confusion
Use UAGs for phased rollouts: Create a "Beta Users" UAG with new features enabled before rolling out to the entire organization
Consider feature dependencies: Some workflows require multiple features (e.g., full shipment lifecycle needs Command Center + Temperature Release)
Test feature combinations: Verify workflows work correctly with your specific combination of enabled features
π Tag management best practices:
Keep tag taxonomy simple: Use clear, hierarchical tags (e.g., Region > Country > City) rather than overlapping categories
Tag at appropriate granularity: Tag shipments at the level users need to see them (customer-level, region-level, or lane-level)
Avoid too many tags per UAG: Users in UAGs with many tags may see more data than they need - keep groups focused
Review tag usage regularly: Check which tags are actually being used on shipments and adjust UAG configurations accordingly
π Search tips:
UAG search is case-insensitive - type "kentucky" to find "Kentucky Lane Viewers"
Search matches partial names - type "lane" to see all lane-related groups
Search updates results as you type for quick filtering
π§ Email entry tips:
Copy-paste email lists directly from spreadsheets or other tools
Mix comma and space separators - system handles both formats
Remove duplicate entries before sending (system prevents them automatically)
Invalid email formats are rejected immediately with clear error messages
Common Issues & Fixes
User canβt see data
Check group tags
Ensure data is tagged correctly
User sees too much data
Check all groups the user belongs to
Remove unnecessary group memberships
User canβt access features
Verify at least one group has the feature enabled
Cannot create group
Enable at least one feature
Tags not working
Ensure tags match exactly between:
User Access Group
Data (shipments, lanes, etc.)