stoplightio
User Permissions
When managing an organization the current user permissions are difficult for the number of people we use. We are slowly moving our engineering teams to Stoplight to streamline publishing and its becoming difficult to manage users and teams at this level. An estimated 50 - 70 users are expected over time.
It would make more sense to have An Organization Admin - Someone who can hand out logins and set permissions for each user in the organizations.
Team Admin: What they can do:
- can create a projects in the organization
- add users ALREADY in an organization to a project.
- Publish a project to the web What they can not do:
- Edit other projects
- Add users who are not apart of the organization. They need to reach out to the organization owner for that.
Contributer: What they can do:
- Read and write to projects they are added to
- Publish projects they are added to
Right now a contributer can not publish and must be made an admin. This is starting to become a big problem since to fix it, they have to be made an admin at the team level.
Also making someone a reader at the organization level then a contributer on a team level does not allow them to create projects. It tells them they are a reader in the organization and need to have the permissions updated. This is the biggest headache since we need to hand out higher level permissions to users than is necessary or create the project for them.
Creating a team should allow them to create, edit, delete and publish their own projects without being able to affect other organization projects.
@tatiana-perry the current architecture makes some of this a bit difficult now, and we totally feel your pain. We're going to be making some changes though to make this more possible though.
I appreciate you writing this all out. We'll add it to the internal design conversation.
I'll see if we have any helpful workarounds internally.
