What It Does
Explains sales records that may appear beside CRM and project work.
This article is written for help desk users who need a simple, practical explanation of the feature and the checks to make before saving changes.
When To Use It
- Use it when setting up or reviewing this feature for a company.
- Use it when a user asks where the feature is or why the expected record is missing.
- Use it before importing, approving, publishing, syncing, or reporting data related to this area.
Before You Start
- Confirm you have permission to use the screen.
- Check that required setup records already exist.
- Review the record before saving changes.
Basic Steps
- Create or open the project, task, client, or CRM record.
- Add ownership, dates, status, and priority details.
- Use notes, files, bugs, timelogs, or discussions to track progress.
- Review dashboards or boards to manage workload.
- Close or report on the work when complete.
Practical Example
A project manager creates a client implementation project. They use invoices estimates and sales orders to add tasks, assign owners, record discussions, track time, and review the board before the weekly client update.
Common Mistakes
- Skipping the setup record that the screen depends on.
- Saving without checking employee, date, or status.
- Assuming all users can see the same menu.
- Not verifying the result after the change.
What To Check If Something Looks Wrong
- Confirm the employee, company, department, location, or date range is correct.
- Confirm the user has both module access and role permission.
- Check whether the record is filtered out by status, date, location, or department.
- Review related logs, history, or reports before changing production data.
Related Articles
- Projects And Tasks Overview
- Creating And Managing Projects
- Task Management List Grid And Scrum Views