Projsite documentation
Reference
Troubleshooting and a glossary of core Projsite terms.
General troubleshooting steps
- 1
Check context
Confirm the correct account, company, project, warehouse and date range.
- 2
Check access
Review membership, role, permissions and current status.
- 3
Check data
Check required fields, filters and the underlying source.
- 4
Refresh
Refresh or reopen the view.
- 5
Escalate
Contact support if the problem persists.
Visibility and unavailable actions
If a project or booking is missing, check account, membership, invitation, dates, filters, context and status. If edit or approval is unavailable, the role may be insufficient, status incompatible or the action may belong to another route location.
Time, zone and Magic Inbox
Check restrictions, resource and zone conflicts, time rules, locations and required data. For Magic Inbox, check project address, successful sending, file type, the 15 MB limit, clear source fields and source metadata.
Inventory, ledger and codes
For stock discrepancies, check current stock, reserved quantity, related bookings, ledger, location and adjustments. A code may be deactivated, linked elsewhere, unreadable or absent in the current environment.
Notifications, Intelligence, AI and weather
Notifications depend on recipient role and preferences. Missing metrics can result from missing activity or fields; missing data is not zero. If AI conflicts with a metric, use the structured metric. Weather requires usable location data, external availability and forecast coverage.
Related documentation
- arrow_forward
Projects and access
Roles and permissions
Role-based access distinguishes membership, roles, broad booking permissions and specific status transitions.
- arrow_forward
AI and supporting data
Magic Inbox
Magic Inbox is Projsite’s AI-assisted workflow for turning incoming delivery information into structured booking proposals.
- arrow_forward
Projsite Intelligence
Insights, recommendations and data quality
AI can identify changes and patterns, but result quality depends on source data and should be treated as decision support.