Contact Credit Access
Lets your Contacts administrators maintain a partner's credit limit and follow-up responsible without handing them a full accounting role. Natively these two fields are locked to accounting groups; this module loosens that restriction so members of Contacts "Administrator" can read and edit them.
Lets your Contacts administrators maintain a partner's credit limit and follow-up responsible without handing them a full accounting role. Natively these two fields are locked to accounting groups; this module loosens that restriction so members of Contacts "Administrator" can read and edit them. Requires Odoo Enterprise — this module depends on account_followup (the Enterprise Follow-up app), plus contacts and account. It does not install on Community.
What it actually does (honest scope)
This is an access-widening module, not a lock-down one. It redefines the field-level groups on two fields so that base.group_partner_manager (Contacts / Administrator) is added to the list of groups allowed to see and change them:
credit_limitfollowup_responsible_id(from Follow-up Levels)
Users who are in none of the allowed groups still cannot see or change these fields — that restriction is enforced natively by Odoo's field-level security, and this module does not remove it. It only adds the contact-manager group to the allow-list.
Features
- Contact managers can maintain credit limit and follow-up responsible directly from the contact form.
- No accounting role required for those two specific fields.
- Two field redefinitions only — no new models, no data, no automation.
Configuration
1. Install the module (Enterprise account_followup required). 2. No settings. Users in Contacts → "Administrator" immediately gain read/write on the two fields.
Limitations
- Widens access rather than restricting it — grant Contacts "Administrator" only to people you intend to trust with credit limits.
- Only the two fields above are affected; other accounting-gated fields remain restricted.
- The two fields are Enterprise/accounting fields, so the module is Enterprise-only by nature.
Tests
Automated tests run on Odoo.sh staging (Enterprise dependency; not runnable on the Community lab).
Screenshots: TODO (capture from staging).
Built and maintained by ETS.inc — support via the address on this listing.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module