Table of Contents

Overview of Teams

HgLab provides the most value when it is used by your whole team. Developers might be allowed to push code to specific branches of your repositories, but not merge these changes into mainline. Release Engineers may be the one responsible for merging these changes in, and Project Administrators get a permission to create new Repositories. To facilitate these scenarios, HgLab supports a permissions system based around the concept of Teams. You can manage Teams for each Project individually.

Teams in HgLab

Teams formalize the idea that the same one User can be a Rockstar Developer in one project, an Awesome Tech Writer in another one, and a Project Manager in some third project. Unlike Groups, which have the same membership throughout HgLab, Teams allow different Users to assume different Roles in different Projects.

Roles are created in the Administration Area. See Accounts article for more information.

Adding Teams

To add a Team to the Project, you need to have a "Team Management" permission. Click the "+ Team" button on the Teams page and you'll see a dialog:

Teams in HgLab
The name for the Team. It is automatically slugified and the slug can later be used in @mentions.

Team Roles and Members are assigned and added later.

Managing Team

On the Team page you'll see three lists: a checkbox list of Roles and two lists with Users and a Groups. To add a User to the Team, start typing username into the input and click + User to add the selected user. The same is done for Groups.

Teams in HgLab

comments powered by Disqus

Take HgLab for a Spin

Try HgLab now. Full-featured 45-day evaluation, no credit card required.