I'm using django-filebrowser-no-grappelli, but I think this is a question not only affected to the fork.
What triggers the creation of the FileBrowser permissions (like "filebrowser | FileBrowser | Can view FileBrowser") you can assign to users and groups?
On the machine where I first installed FileBrowser, the permissions are assignable and also found in the database. On other machines, the permissions are missing.
Sorry if this question has already been asked.
I'm using django-filebrowser-no-grappelli, but I think this is a question not only affected to the fork.
What triggers the creation of the FileBrowser permissions (like "filebrowser | FileBrowser | Can view FileBrowser") you can assign to users and groups?
On the machine where I first installed FileBrowser, the permissions are assignable and also found in the database. On other machines, the permissions are missing.