Flutex provides access for Perfex customer contacts. The customer is the company/account that owns records; the contact is the individual who signs in.
The API reuses these contact permission keys:
The app uses customer information and permissions to present available features. The server independently validates permissions and record ownership on each protected operation.
Project settings can further restrict tasks, files, milestones, discussions, and financial information. Ticket visibility can also depend on contact-only rules. There is no general permission in this documented contract that gives a contact unrestricted staff access.
An authorized CRM administrator should open the intended contact, adjust its customer permissions, and save the changes. Refresh the app’s dashboard or sign in again, then verify the affected feature with that contact.
If a record is still unavailable, check its customer ownership and customer-visible status. An administrator seeing it in Perfex does not prove that a contact should see it.
Company editing is restricted to the primary contact in the inspected app and API workflow. A primary contact is still a customer user, not a CRM administrator.
Never work around a permission failure by changing the mobile menu alone. Backend authorization is the final authority.