This module adds security restrictions to timesheet amount fields.
It restricts access to cost-related fields in timesheet reports to users who have the "Allow to read analytic costs" permission from the analytic_amount_security module.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Restricts the cost and amount fields in timesheet reports so only users with the 'Allow to read analytic costs' permission can see them.
This module hides money-related columns in two timesheet reports from users who are not allowed to see analytic costs.
- In the Timesheets/Attendance report (
hr.timesheet.attendance.report), the fields for timesheet cost, attendance cost and the cost difference are only visible to members of the permission group provided by the analytic amount security module. - In the Timesheets Analysis report (
timesheets.analysis.report), the monetary amount column is restricted in the same way.
Users without that permission simply do not see these cost columns; users who have it see them as before. No new menus, buttons, checks or automatic calculations are added: the module only changes who can read these existing fields.
It touches the timesheet reporting area and relies on the analytic amount security module for the permission group, plus the timesheet and timesheet attendance modules for the reports themselves.
Depends on
Models and fields (2)
- timesheets.analysis.report · extends an existing modelamount
- hr.timesheet.attendance.report · extends an existing modelattendance_cost, cost_difference, timesheets_cost
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/timesheet.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.