1. Shut down Confluence.
2. Back up your Confluence database.
3. Run the SELECT to check which rows you are going to remove (replace 'KEY' with the space key and 'UPPERCASE-GROUP' with the group name):

select *
from spacepermissions
where spaceid = (select spaceid from spaces where spacekey = 'KEY')
and permgroupname = 'UPPERCASE-GROUP';

There should be one row per permission granted to the group (view, edit, admin, etc).

4. Run the DELETE to remove the rows (again replacing the two variables).

delete from spacepermissions
where spaceid = (select spaceid from spaces where spacekey = 'KEY')
and permgroupname = 'UPPERCASE-GROUP';

6. Start Confluence again.

You can do the same for users by changing the column name 'permgroupname' to 'permusername' in the two queries.

1) Without using the "Group Picker", type the name of the group in lowercase
2) Add this group and grant "Can Use" permission
3) Save
4) Edit the permission and remove the "Can Use" rights
5) Save

Result: The "Can Use" permission is still assigned to this group via UI and in the DB as well.

As a workaround to removing the "Can Use" permission for an individual user/group, please run the following query on your DB:

SELECT * FROM SPACEPERMISSIONS WHERE PERMTYPE = 'USECONFLUENCE' AND PERMUSERNAME = '<Username>'  - For user permissions
SELECT * FROM SPACEPERMISSIONS WHERE PERMTYPE = 'USECONFLUENCE' AND PERMGROUPNAME = '<Groupname>' - For group permissions

Ensure that correct entries have been listed by this query and then delete these entries by:

DELETE FROM SPACEPERMISSIONS WHERE PERMTYPE = 'USECONFLUENCE' AND PERMUSERNAME = '<Username>' - For user permissions
DELETE FROM SPACEPERMISSIONS WHERE PERMTYPE = 'USECONFLUENCE' AND PERMGROUPNAME = '<Groupname>' -For group permissions

Please avoid manually typing in the name of the user or group while adding them to the global permissions, instead use the "Group/User Picker", to avoid this problem.

I definitely need to be able to assign multiple groups access to the same space.

Doug

The problem is most of my users have upper case IDs, so this may start biting...

So if you apply the permissions to the 1st user shown on the UI and save it then it works as intended - the only thing is that your user appears twice on the Space Permission UI.

See attachments "User_KClarke-1.jpg" & "User_KClarke-2.jpg"

Ideally we should always reference user by id in all tables. This will eliminate a big chunk of potential problems and also will make username modifiable. But as it is quite complex we may fix this particular bug first.

Amen to that!!

If http://jira.atlassian.com/browse/CONF-4063 was fixed this problem would most likely not exist.

Atlassian promised us 6 months ago that CONF-4063 will be fixed by 2.7 and we were patiently waiting for the fix because we understand that this is major change in the database schema.

2.7 is out now and no one even touched this issue and we are starting to see more and more issues that are connected to this major flaw in the Confluence db schema.