SBS Project Extension: every delivery fact on the project record

A project is more than a list of tasks. An implementation team needs to know who the client's single point of contact is, which consultant leads it, what the contract is worth and how much has been collected, where the staging environment lives, when the free support period ends, and what the biggest risk is this month. In stock Odoo none of that has a home, so it ends up in a spreadsheet.

The module gives each of those a field on the project, across seven tabs, and gathers the same information into cross-project lists ordered by priority, so a delivery manager can read every project in one place on a Monday morning. Review sessions cover several projects at once, and every review line added, changed or removed is recorded in the session's chatter with its old and new values.

The Credentials tab is a convenient place to record which server and database a project uses, not a vault. Its environment passwords are stored and displayed as ordinary text. Only holders of the credentials role can open the tab or the Credentials list, but the passwords are not encrypted and anyone who can reach the database can read them. For secrets that need encryption at rest, an identity check before revealing, and an audit trail, use a dedicated credential vault instead.

When a delivery is signed off, an administrator can Lock the project. Its fields and its linked detail records stop accepting changes, and an attempt to edit one is refused by name. A lock freezes what the project is, not what is said about it: review sessions and review lines remain fully writable, so a frozen project can still be reviewed.

Time on tasks is counted rather than remembered. The elapsed time between Start and End is measured by the server, and when the timer stops the user can reduce it, never increase it, before it becomes a timesheet line. Where guesswork is not acceptable, a Project Manager can require that time reaches a task only through the buttons.

Access is split by role, so credentials and financials are visible only to the people who need them. Task visibility is set separately from project access, so somebody can read project information without touching tasks at all.

Two consequences are worth planning for. Only an SBS Project Admin can create a project: anyone else is refused, including other applications creating a project on a user's behalf, such as from a sales order, so grant the role to whoever, or whatever, needs to create projects. And the lock field can only be changed by the Lock and Unlock buttons: writing it directly is refused even when the value is unchanged, so an import or data load that writes a project's full field set will fail. Exclude that field from such loads.

We tested every workflow on this page on a live Odoo 19 Community database, including the Start/End-only restriction, which the server enforces rather than merely hiding. Multi-company use and the interaction with Odoo Enterprise's own task timer have not been tested yet. Enterprise ships a competing Start/Stop control in the same task header, so expect two timers if you install this module on Enterprise.