Hi guys -
I just saw the pricing updated to allow for unlimited team members...which is great...but unfortunately still unusable for an organization due to the lack of security/team management functionality that exists.

For example:

• I have developers that I need to add a to a service so they can manage and manipulate test microservices

• The linked services in the other environments, namely, "Production", are available to them as a Member, or Admin (obviously), which you give them access to that project. So now, Junior Developer John Doe has access to both dev AND production environments.

Similarly, we have situations where a single user needs access to one of the services, but we dont want them being able to view, even in dev, the database settings, or associated environment variables to a secondary service in that project and environment.

Net net, in my opinion, adoption for production ready organizations is going to be greatly limited just by the security offering here. We only have 3 people in our environment currently out of many dozens of developers, and as such, we have very little ability to migrate the majority of workloads.

I'd suggest that Railway considers adding Team Member settings to both the Environment AND the Service itself. Adoption for at least our team would be 10x.

You're building a great product...those of us who use it love it...but we can't make it much further until we have some control over who can see and do what.

JE