Usage in internal network

[pni...@gmail.com]

We want to use Openwisp in the internal network of a company.

Can everything about organizations be removed from the frontend? If possible, do not modify the models, simply hide all the fields to select organization and that there is an organization in the database.

Would it be possible to do it without having to overwrite all the applications?

[Hardik Jain]

Hi, I think you are looking for:

https://docs.djangoproject.com/en/3.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.exclude

https://docs.djangoproject.com/en/3.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_exclude

You can use either of them as per your use case. I am not sure if the form will break, if it does you can always use simple CSS and set display: none to what you interested in hiding.

Also, this question is more related to Django than OpenWISP, if possible consider using Stack Overflow or any similar platform for similar queries.

Regards,

Hardik Jain

[Federico Capoano]

I suggest to simply use one organization and leave everything as is.

One improvement we can do, and I would welcome that, is to make the organization selection automatic when the user has access to only one organization.

I had this in the back of my mind for some time and now I finally created an issue for it: https://github.com/openwisp/openwisp-users/issues/170

If we do this change, you may then just use OPENWISP_ADMIN_THEME_LINKS to supply a custom css which hides the organization field.

I think that would be enough and would keep it simple for you. Overriding that part may cause you unnecessary headaches.

[pni...@gmail.com]

I tried with this last week without success (but remember I'm very new to openwisp, django an python).

I couldn't do it with monkey patching the  OrgMixin class. If remove from fields, database fails with "organization cannot be NULL" when saving.

I did not manage to modify the default value with monkey patching, but yes modifying directly the OrgMixin class.

I will try again.