MINI ODOO (CRM) CUSTOMIZATION ON VPS. EVERYTHING IS SET FOR YOUR WORK. PYTHON! USD 30!

PLEASE DO ONLY APPLY for this job if you are an absolute ODOO EXPERT and know how to tweek which Python and Conf files.
I am a programmer myself and know that the below changes are minor adjustments for every expert.
After three attempts on Freelancer with people that claimed to be experts but had no clue, I would prefer if you would describe which steps I need to take and which particular files I need to adjust - instead of giving away the login data and watching how the system is destroyed.
(But if you are 100% SURE that you KNOW what you do and have the respective EXPERIENCE.
I can surely hand out the login details).
YOU WILL FIND THE FOLLOWING ELEMENTS READILY INSTALLED ON THE SERVER.
- Debian 12 (Apache) - Odoo 18 (Community/ On-Premise Version) - Let's Encrypt SSL Certifcate (default Apache installation) - Domain.
all DNS files are already properly set on the server - The own email servers are set and work.
The system is working, properly.
I need you to apply changes WITHOUT TRIGGERING AN ODOO SUBSCRIPTION.
Changes need to be applied without "Studio", "Hidden Menu", or other Subscription Apps/ Modules.
I NEED NO CHANGES REGARDING THE ADMIN.
I need a very simple setup for a very simple project at this time.
The Administrator's full access and record rights can be left untouched.
He should simply be able to see, do, and change everything (default).
CHANGES OR IMPLEMENTATIONS REGARDING THE OVERALL SYSTEM.
1.
The installed SSL certificate (Let's Encrypt installed via ISPConfig) works properly on the domain.
However, it still needs to be integrated into Odoo (port still shows "unprotected connection").
This probably needs to be adjusted via [login to view URL] or "System Parameters" or both.
You are the Odoo expert and know how to execute the integration of Let's Encrypt Certificates.
2.
Please eliminate the "Group Chat" from "Discuss".
The Administrator should be able to communicate with users 1.
via Discuss (= via the chat function of the CRM module).
But users should not be able to contact and see other users.
CHANGES REGARDING (NORMAL) USERS WHO ARE NOT THE ADMINISTRATOR 1.
Normal/new users ("User Template") should just be allowed to see the CRM module and NO OTHER MODULE - even if the Administrator adds new apps in the future (these apps are for the use of the administrator and not for the users).
Normal users should not be able to see the "Settings", "Discuss", "Apps", "Contacts", "Calendar" modules/apps, etc.
!They are just allowed to see and access the CRM module! 2.
Normal users can already see their "Own Documents Only".
However, users should ONLY BE ALLOWED TO see their very own contacts (that they file into the system via the CRM “New” button or that they are given by the Admin).
THE PROBLEM.
When a NEW contact is created in the CRM system, the first field is [login to view URL] or partner_id.
This field is defined as a Many2One field that refers to [login to view URL] and comes up with a drop-down menu.
This drop-down menu shows EVERY staff member, ALL employers, ALL Contacts, and Leads ever created - and not JUST THE OWN CONTACTS.
This mustn’t be.
This drop-down list should be restricted to see the VERY OWN CONTACTS in the drop-down list or, alternatively, this drop-down list should simply NOT pop up at all (this second alternative is fine if this is the best, safest, and easiest way to handle this problem).
This can be handled via Python by disabling the drop-down list.
The [login to view URL] or partner_id field should surely keep its functionality in the overall module (storing new contacts).
PLEASE apply these changes in Odoo On-Premise/ Community Version running on a Virtual Server WITHOUT triggering an Odoo Subscription.
WITHOUT "Hide Menu", "Studio" or other Subscription apps.
Python Linux Arquitetura de software SSL Odoo ID do Projeto.
# Sobre o projeto 49 propostas Aberto para ofertas Projeto remoto Ativo em Recentemente