odoo/documentation#18938
Created by Merel Geens
Blocked
- Merge method
- Review
-
CI
- ci/documentation: (runtime 918s)
- ci/codeowner_coverage: (runtime 5s)
- label
- odoo-dev:17.0-rem-archive-main-admin-user-warning
- head
- d4bbaf39dd1a84385d0a3e2d65826869fd0339a7
| odoo/documentation | |
|---|---|
| 17.0 | #18938 missing r+ |
| 18.0 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| saas-19.1 | |
| saas-19.2 | |
| saas-19.3 | |
| saas-19.4 | |
| master |
[REM] applications: warning about deactivating the admin user
The warning is redundant because Odoo prevents you from archiving the currently logged in user. The only way you'd be able to remove access from a database by archiving an admin user would be to do so for all admin users as the superuser. The superuser section of the access rights page warns against locking yourself out that way:
https://www.odoo.com/documentation/19.0/applications/general/users/access_rights.html#superuser-mode
It also causes confusion, because Odoo has a default admin user with an id defined in the external reference base.user_admin. If code relies on that user being present, it can indeed cause problems when archived. But Odoo should support that use case, and be robust against it. You should be able to archive the default admin user. See the discussion in odoo/odoo#264352 .
If you ask odoo.com/help if you should be able to archive the default admin user, it'll say you should never do that citing this section.
Hence this change removes the section altogether. The main risk for locking yourself out of your database is changing access rights, and the documentation page for that has multiple warnings about it. Unless you are the superuser or use direct SQL, you should not be able to lock all admin users out of the database through archiving in the UI.