Permissions within Teams | Feature Requests

Render

Create

Roadmap

Feature Requests

Changelog

Permissions within Teams

planned

danielle

Teams should have more granular permissions that determine who has access to specific features within that team. For example: only let some people suspend/delete services.

May 14, 2020

Andy Fang

This is such a crucial feature, it would be a godsend if Render could make incremental releases just so there's a separation between Admin.

Anurag Goel

Merged in a post:

Roles to team members

Yashu Mittal

Here are few suggestions for the roles which can be added to the teams.
* Developer
* Manager
* Billing
* Admin

July 17, 2020

May 28, 2021

Anurag Goel

marked this post as

planned

Aldric Giacomoni

I would be happy with someone else who's able to modify settings for the app.

developer

I also need this functionality. Specifically, adding a second admin to view billing for a particular team. This is because I set up a team on behalf of a client, but eventually want them to manage the team.

Sergiu Truta

Even just two roles, admin and dev are good enough for the beginning, as I only want some members of the team to be able to erase services, databases, etc, but of course also having Billing and other roles would be great!

Moiz Virani

This is top priority for us right now!

Daniel Meechan

It'd be useful to restrict who can change settings, like the databse access control list. To restrict who can add their IP to the database ACL and connect to the live DB

Alex J

I would like to

grant people to only see e.g. build status
hide env vars (not even me as an owner needs to see those more than once, they could be encrypted)
protect services/dbs from deletion (even from owners without manually unlocking first, similar to how aws dbs can be set)

Kenneth Pedersen

Important one! Some of the most successful companies in the world were founded by outsourcing software and various organizational responsibilities. Software outsourcing has some definite advantages; it can improve overall quality, reduce costs, and increase focus within the company on essential matters, but it also spawns some significant IPR risks. It is crucial to connect to the ready-made part of the secure software and treat it as a "black box», by letting only selected members have access to specific features. Hope this will get priority. Thanks Render, you are doing an awesome job.

→