ODOO (CRM) CUSTOMIZATION ON VPS. EVERYTHING IS ALREADY SET UP FOR YOUR WORK. SEE DESCRIPTION. -- 2

For a client, I have just set up a VPS with Odoo.
YOU WILL FIND THE FOLLOWING ELEMENTS READILY INSTALLED.
- Debian 12 - Odoo 18 (Community/ On-Premise Version) - Let's Encrypt SSL Certifcate - Domain - Gnome (if you would like to use a Graphical Interface) - KDevelop (as the software to manipulate Python and PHP) 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.
We need a very simple setup for a very simple project at this time.
The Odoo Administrator/ Master user is not of importance regarding your help.
The Administrator's full access and record rights can be left untouched.
He should simply be able to see, do, and change everything.
CHANGES OR IMPLEMENTATIONS REGARDING THE OVERALL SYSTEM.
- The installed SSL certificate (Let's Encrypt) works properly on our 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.
The system needs to be protected as well as the emails.
- The Outgoing and Incoming email servers need to be adjusted according to the domain that is linked to the VPS and Odoo.
I can provide all needed data.
However, as you probably know, Odoo creates a sample email (info@Domain) during the setup.
I am not aware of the default "user" name and default "password".
Thus, this info need to be extracted or provided by you (you probably know the default values).
- Please ensure that new emails can be created on the basis of the underlying domain data within Odoo (by the administrator! Not by users!).
- Please eliminate the "ChatBot" as well as the "Group Chat" from "Discuss".
The Administrator should be able to communicate with users 1.
and users should be able to contact the Administrator 1.
via Discuss or the chat function.
But users should neither see the horrible ChatBot nor be able to contact and see other users.
The only contact ("Discuss"/ Internal Chat) that they should see is the Administrator.
And the Administrator should be able to see all users in separate chats and to contact them.
- Push Messages should be turned on (people should notice in case they are contacted.
The ChatBot asks users to enable this function.
They should not be asked.
This function should be enabled by default).
CHANGES REGARDING NORMAL USERS (AND NEW USERS --> USER TEMPLATE) - Normal/new users ("User Template") should just be allowed to see the CRM module and NO OTHER MODULE.
I have already adjusted the CRM Pipeline as their "Home Action" that they can see once logged in.
They should not be able to see "Settings", "Discuss", "Apps", "Contacts", "Calendar", etc..
Nothing.
They are just allowed to see and access the CRM module.
- I have already adjusted the system in the sense that normal users can 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 where I need your help with.
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 dropdown menu.
This dropdown menu shows EVERY staff member, ALL employers, ALL Contacts, and Leads ever created in a searchable way - and not JUST THE OWN CONTACTS.
This mustn’t be.
This should be restricted in the sense that users can either only see VERY OWN CONTACTS in the drop down list or, alternatively, this drop down list should simply NOT pop up at all (this second, bad alternative is ok if this is the best way to handle this problem).
The field should surely keep its function in the overall module (storing a new contact).
- Furthermore, via the top right user menu of Odoo, users should not be able to see or access and alter the database and they should not be able to see the company’s “Odoo Subscriptions”.
PLEASE TELL ME WHAT YOU NEED IN ORDER TO IMPLEMENT THESE CHANGES.
I need to know, what you need to apply these changes on Odoo On-Premise running on a Virtual Server WITHOUT Odoo Subscription; id est.
WITHOUT the "Studio" App, without the "Hide Menu" app, and without the optional Odoo Python app (you know that you have alternative ways to edit Odoo's source code).
What will you need to not trigger a subscription (don't buy or activate apps)? Is the access to Odoo as Administrator sufficient to apply these changes? Or will you need access to the VPS (to the new Debian 12 server as described on top of the page) in order to manipulate Python Code and adjust the Configuration Files? I am looking forward to your bid and to your comments.
PHP Python Arquitetura de software Ubuntu Odoo ID do Projeto.
# Sobre o projeto 22 propostas Aberto para ofertas Projeto remoto Ativo em 41 minutos atrás