MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 3 Releases 96 Wiki Activity

feat(orgs): auto-create default teams on org creation #513

New Issue
Open
opened 2026-06-06 15:51:10 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-06 15:51:10 +00:00
Owner
Copy Link
Copy Source

Summary

When a new organization is created, automatically provision a set of default teams with standard permission levels. This reduces manual setup and ensures consistent access control across all orgs.

Default Teams

Team Permission Description
Managers Admin Full org admin access
Sysadmin Admin Infrastructure and deployment access
Developers Write Code contributors
QA Write Testing and quality assurance
Design Read Design review access
Support Read Customer support read access

Behavior

  • On org creation, auto-create the default teams listed above
  • Org admins can customize, rename, add, or delete teams after creation
  • Default teams are configurable in Org Settings (admins can define their own presets)
  • The creating user is automatically added to the Managers team

Org Settings

Add a "Default Teams" section in Org Settings where admins can:

  • View and edit the default team presets
  • Add custom default teams
  • Set default permission levels per team
  • Toggle which teams are auto-created for new repos

Authored by Jonathan Miller (@jmiller)

## Summary When a new organization is created, automatically provision a set of default teams with standard permission levels. This reduces manual setup and ensures consistent access control across all orgs. ## Default Teams | Team | Permission | Description | |------|-----------|-------------| | Managers | Admin | Full org admin access | | Sysadmin | Admin | Infrastructure and deployment access | | Developers | Write | Code contributors | | QA | Write | Testing and quality assurance | | Design | Read | Design review access | | Support | Read | Customer support read access | ## Behavior - On org creation, auto-create the default teams listed above - Org admins can customize, rename, add, or delete teams after creation - Default teams are configurable in Org Settings (admins can define their own presets) - The creating user is automatically added to the Managers team ## Org Settings Add a "Default Teams" section in Org Settings where admins can: - View and edit the default team presets - Add custom default teams - Set default permission levels per team - Toggle which teams are auto-created for new repos --- *Authored by Jonathan Miller (@jmiller)*
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority Medium
Type Feature
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#513
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?