mirror of
				https://github.com/zulip/zulip.git
				synced 2025-11-04 05:53:43 +00:00 
			
		
		
		
	This commit does not add the logic of using this setting to actually check the permission on the backend. That will be done in a later commit. Only owners can modify this setting, but we will add that logic in a later commit in order to keep changes in this commit minimal. Adding the setting breaks the frontend, since the frontend tries to find a dropdown widget for the setting automatically. To avoid this, we've added a small temporary if statement to `settings_org.js`. Although, most lists where we insert this setting follow an unofficial alphabetical order, `can_manage_all_groups` has been bunched together with `can_create_groups` since keeping those similar settings together would be nicer when checking any code related to creating/managing a user group.
		
			
				
	
	
		
			22 lines
		
	
	
		
			531 B
		
	
	
	
		
			Python
		
	
	
	
	
	
			
		
		
	
	
			22 lines
		
	
	
		
			531 B
		
	
	
	
		
			Python
		
	
	
	
	
	
# Generated by Django 5.0.8 on 2024-09-05 08:34
 | 
						|
 | 
						|
from django.db import migrations, models
 | 
						|
 | 
						|
 | 
						|
class Migration(migrations.Migration):
 | 
						|
    dependencies = [
 | 
						|
        ("zerver", "0592_set_can_manage_all_groups"),
 | 
						|
    ]
 | 
						|
 | 
						|
    operations = [
 | 
						|
        migrations.AlterField(
 | 
						|
            model_name="realm",
 | 
						|
            name="can_manage_all_groups",
 | 
						|
            field=models.ForeignKey(
 | 
						|
                on_delete=models.deletion.RESTRICT,
 | 
						|
                related_name="+",
 | 
						|
                to="zerver.usergroup",
 | 
						|
            ),
 | 
						|
        ),
 | 
						|
    ]
 |