Main error cases
Generally, when problems occur related to viewing, editing, or creating information on the platform, there is a high chance that the cause is linked to the user's access level.
This happens because each profile (such as operator, supervisor, or manager) has specific and limited permissions. Therefore, if the user has a profile that does not include a certain action or feature, they will not be able to view certain menus, edit records, or create new items.
Thus, whenever this type of situation arises, it is important to first check the access level configured for the user, as this is usually the most frequent cause of the problem.
Examples of problems related to access level:
The "Settings" and "Pipelines" options are not appearing for the user.

Analysis of the possible problem:
In the platform's permission structure, certain menus and resources are only visible to profiles with a higher access level, such as manager or supervisor. When the user is configured only as an operator, these options are automatically hidden, as this profile has restricted access only to day-to-day operational functions.
Recommended solution:
It is necessary to verify the user's current profile. If they are indeed set as an operator, request the support team to change their access level to manager or supervisor.
After this update, the user should be able to view the "Settings" and "Pipelines" menus normally.
The "Company Name," "Contact Name," and "Responsible" fields do not display records when clicking the dropdown

Analysis and Solution:
Previously, these fields displayed only the first 10 records as suggestions.
Since the module is very extensive and these initial records rarely matched what the user actually needed, the functionality was adjusted: now suggestions only appear when the user starts typing, from the third letter onward.
In other words, this is not a bug, but rather a performance and usability improvement.
Furthermore, remember that within the system, Company and Contact are always related:
- If the Company field is filled, the Contact field will only show contacts linked to that company.
- If a Contact is selected, the company search will be automatically filtered according to that contact.
Unable to transfer responsibility in the Poli Flow
When trying to transfer the responsibility of a card/ticket in the Flow and failing to perform the action, one of the most common reasons is that the target user is not linked to the specific pipeline.
In this case, it is necessary to verify if the user is indeed associated with the pipeline before completing the transfer.










