Poor user management for toolchains wastes time and money. User management mostly boils down to the giving and restricting of permissions for users. It’s also known as permissions management but at Eficode ROOT we like to call it team management!

User management for software tools needs to get better

Sometimes companies pay providers to manage permissions for them which costs a pretty penny. But then again, when development tools are managed in-house by corporate IT, developers have to request access to development tools from someone who’s not a member of the project, which wastes time as they wait for those permissions to arrive. This could take days. Impatient teams are tempted to take up ad-hoc practices such as sharing passwords and user accounts, which is a security risk.

 

ROOT Team Management: A centralized, self-service user management system

One of the cornerstones of ROOT as a software production line is to make permissions management easier and faster for users. ROOT does this by giving users a centralized place for self-service permission management. Thousands of users in the field of digital product building rely on ROOT to provide them everyday improvements like these.

 

How does ROOT’s Team Management (RTM) work?

Trained, in-house application administrators

Eficode ROOT will train a few key users from your teams to act as application administrators. (They can request help from Eficode ROOT's system administrators whenever they need it.)

These administrators can then give ‘normal users’ permissions to act as group and bot administrators, so that these users can give other users access to said groups and bots.

Batch permissions: Groups

Most companies that use Eficode ROOT choose a setup which has one group that grants access to, for example: a team's JIRA project, code repositories, dashboards, documentation, automation tools, and so on.

This group is usually administered by a team lead/project manager and they grant developers membership, and thereby normal access, to all the tools in the group. When a user is granted group membership, the membership federates across the whole platform giving the user permissions to whatever the group has permissions to.

 

A further look under the hood of ROOT Team Management

Over the years, we have used and experimented with various user management systems, however each of them were missing features or were otherwise not suitable for ROOT users. That is why we decided to develop our very own user management system. Enter Eficode's ROOT Team Management, or RTM for short.

Compatible with (practically) all tools

  • RTM is implemented on top of OpenLDAP which means that it is compatible with all LDAP compatible systems – which is to say pretty much every tool out there.
  • You could, for example, synchronize all developers from your corporate AD to RTM and control development tool permissions in one place.

Bots (technical/automation accounts) and an extensive API

  • In addition to offering the basic user management functionality (user and group management), ROOT Team Management also offers bots (technical/automation accounts) and an extensive API.

Automate it all!

  • The application itself has been developed with the idea that everything should be possible to automate, which means that given sufficient permissions, every action in RTM can be performed through a REST API call.

 

And we’re only just getting started!

Now that the base implementation is complete, we plan to add more features that have been requested by our customers over the years. These include but are not limited to:

  • nested groups,
  • out-of-the-box capability for Single Sign On (SSO) in ROOT installations,
  • customizable visualization (e.g. customer colors and logo),
  • free-to-join group concept
  • close-knit integration to the platform's center piece ROOT Hub
  • our upcoming analytics product Track and Drive.

Watch this space, and have fun working faster and more effectively than before.

 

Published: Jan 16, 2019

Updated: Mar 26, 2024

DevOpsEficode ROOT