7 months ago
We have many team members who are most suited to the deployer role where they contribute to our products, but do not manage and maintain our infrastructure. They should not be able to modify project settings, services, or environment variables for example. But they do contribute code and generate PRs that require PR environments in Railway so they can test their changes.
After changing the team members to Deployer we found that it does not support PR env creation and the Member role is required. I'm hoping there is a solution to this so we can better protect our project related settings.
1 Thread mentions this feature
5 Replies
7 months ago
Good suggestion - created a ticket for Product, will keep you posted.
7 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
7 months ago
❌ The internal ticket Support PR Envs for Deployer Role has been marked as canceled.
7 months ago
OK I heard back - unfortunately we cannot provide this via the Deployer role due to some permission constraints in the architecture. You would need to upgrade those users.
Sorry!
7 months ago
Thanks for the quick follow up. I totally understand there are architectural constraints. That said, I think this seems like a reasonable and common use case - where one team (infra/platform) manages settings, and others (product/feature teams) need to deploy and test their changes without having full access to modify project configuration.
Would it be possible to explore adding support in the future for more granular permissions within roles?