-
Notifications
You must be signed in to change notification settings - Fork 40
Description
Describe the bug
When creating a new database using the Guided Setup (#6671) tool, the specifyuser_spprincipal and spprincipal tables are skipped. I imagine this was done due to our desire to remove Specify 6 legacy tables from the system.
After running the setup, going to the Security & Accounts page results in the following error:
ProgrammingError at /permissions/list_admins/ (1146, "Table 'blankdb_grant_2026_01_08.specifyuser_spprincipal' doesn't exist") Request Method: GET Request URL: http://blankdbgrant20260108-issue-2931-1.test.specifysystems.org/permissions/list_admins/
The main issue here is that app resources can be organized into "User Types" (or "User Groups" as shown in Security & Accounts). That means an administrator can assign a particular view definition or other app resource to a 'group' of users easily within a collection. Without the use of the spprincipal, there is not a viable migration option for those already using this feature other than duplicating these resources for every user in a group.
I suggest that we remove the "Specify 6 permissions" section, but retain "User Group" (and standardize the naming between app resources and security & accounts...) so that this functionality remains.
