Introducing Teams and Synchronization of Members from Github
Product
We are introducing “Teams” today, a new feature to improve access controls for your Tideways organization, after several weeks of testing with selected customers.
With Teams you can grant more fine-grained access to your applications, based on team membership of your users. Additionally this feature allows you to automatically synchronize teams and member accounts from your existing Github organizations and save a lot of work on user maintenance.
Until now Tideways had a very simple access control system that allowed admins to invite as many members as they want into their organizations and those members are able to see all applications. For big organizations this is usually not good enough and the manual invitation process is very time consuming and requires care when persons leave the organization.
The team feature is available for organizations with Medium plans (20M+). For our Tideways On-Premise solution, this feature will allow you to synchronize teams from LDAP. The Teams feature is entirely optional and you can still use the simple ACL model from before if you don’t need this much control.
Please see the documentation for more information about how to use it.
About the author
I am the founder and CEO of Tideways. I started the company over 10 years ago with the mission to move the PHP ecosystem forward, starting with performance. As managing director, I work across product, strategy, and the day-to-day of building a developer-focused SaaS business.
I’m a core contributor to the Doctrine open-source project and a founding board member of the PHP Foundation, which reflects my long-standing commitment to the PHP ecosystem. I particularly enjoy working at the intersection of application performance, developer experience, and the open-source community that makes PHP what it is. Outside of work, I enjoy board games, hiking, and coffee.