Getting Started
A practical first-run checklist for enabling Tools Hub, preparing access, and training the first users.
Before You Begin
- A working ERPat tenant or main database with the module installed.
- Administrator access for first setup and a non-admin test account for validation.
- A named business owner who can approve statuses, labels, templates, and reports.
- Module migrations should be applied before live users create records.
First-Run Setup Checklist
- Confirm the module is enabled in Settings > Manage Modules and that the sidebar item appears for an administrator.
- Review the module purpose with the owner of the workflow before users start entering real records.
- Assign role permissions for create, update, delete, settings, reports, and any special management actions.
- Open the first screen from the left menu and confirm list pages, modal forms, and detail pages load without warnings.
- Create or verify starter records such as categories, statuses, templates, locations, teams, or settings that the workflow depends on.
- Run a small end-to-end sample using a non-critical record, then confirm the expected report, dashboard, public page, or downstream handoff updates.
- For API-facing workflows, confirm API credentials, scopes, and expected response examples before sharing endpoints.
Starter Data to Prepare
Core records
- tools
- tool_versions
- tool_views
- tool_daily_stats
- tool_likes
- tool_comments
- tool_results
- tool_logs
Configuration records
- Role permissions for tools, tools_create, tools_update, tools_delete, tools_moderate.
- Sidebar and default menu placement for Tools Hub, Tools Overview, Tools Moderate Comments.
- API routes, examples, scopes, query filters, and response expectations.
Training Path for New Users
- Explain the purpose of the module and what business process it controls.
- Show the main list or dashboard and identify the columns, filters, and action buttons users will touch daily.
- Create one sample record together, then edit it, review it, and complete the expected next action.
- Show where the record appears in reports, related modules, or public/customer-facing pages.
- Review what users should not change without manager approval, especially settings, templates, permissions, and delete actions.