Invoice permissions, visibility, and customer portal
Scope of roles and organizations, actions (permissions), and client view.
Last updated 20 days ago
Invoices access is determined by the user role, organization, and plan features. permissions are typically categorized into viewing all records, viewing one's own records, viewing based on role hierarchy, creating, editing, deleting, and exporting.
With own records rights, one can see Invoices that the user created or where they are assigned as the salesperson. Organization restrictions can further limit the list. If a colleague sees a document but you do not, check the salesperson, creator, organization, role, and active list filters.
Other actions have additional permissions. Creating Payment requires Payments permissions; related Task – Tasks, projects – Projects, and files and Expenses – the relevant module permissions. Therefore, one might be able to see Invoice but lack the permissions to perform a specific action on it.
Editing can be restricted by factors other than just permissions. A document might be sent, paid, exported to accounting, or fall within a locked sales period. In this case, the interface either hides the action or displays an explanation.
In the customer portal, the administrator can hide templates and require a login (Invoices) to view it. The PDF may contain a QR code with a public link. Consider these settings together: the public link must not bypass an enabled login requirement. The methods (Payment) visible to the client are selected within Invoice itself.