Team Membership Management with Fedora Accounts
DRAFT DOCUMENTATION: This documentation is currently in draft form and may not be fully tested and correct. Please verify all procedures before use and report any issues or inaccuracies. |
Overview
This document explains how team membership is managed on Fedora Forge through Fedora Accounts (FAS) groups, and why we don’t use Forgejo’s built-in team management interface. Understanding this system is crucial for administrators and team members who need to manage team membership and access to repositories and organizations.
How Team Membership Works
Fedora Accounts Integration
Team membership on Fedora Forge is managed exclusively through Fedora Accounts groups. This means:
-
No Direct UI Management: You cannot add or remove team members directly through the Forgejo web interface
-
FAS Group Control: All team membership changes must be made in the corresponding Fedora Accounts group
-
Automatic Synchronization: Changes to FAS group membership are automatically reflected in Forgejo team permissions. Users may need to log out and log back into Fedora Forge to see the changes take effect.
How to Manage Team Membership
After making changes to FAS group membership, users may need to log out and log back into Fedora Forge to see the changes take effect. The synchronization happens automatically, but the user’s session may need to be refreshed to reflect the new team membership. |
Adding Team Members
To add someone to a team:
-
Log into
accounts.fedoraproject.org
-
Navigate to the appropriate FAS group (e.g.,
forge-rust-members
) -
Add the user to the group
-
The user will automatically gain access to the corresponding Forgejo team
Want to help? Learn how to contribute to Fedora Docs ›