[GH-ISSUE #3609] [feature]: Changes made by Editor in a Team should be approved by Owner, Full Editor or Reviewer #1247

New issue

Open

opened 2026-03-16 19:29:19 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 19:29:19 +03:00

Owner

Originally created by @syamsoul on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3609

Is there an existing issue for this?

I have searched the existing issues

Summary

New feature that would be great to implement in Hoppscoth is:

New Role in Team which is Reviewer
- Reviewer cannot make changes
- Reviewer can approve/reject changes made by Editor
New Role in Team which is Full Editor
- Full Editor can make changes
- And Full Editor also can approve/reject changes made by Editor
As stated on point 1 and 2, any changes made by Editor must be approved by Reviewer or Full Editor.

So, there will be 5 roles in Team if we implement this.

Owner
Full Editor
Editor
Reviewer
Viewer

Why should this be worked on?

Easy to distribute tasks to team members.
Avoid mistake (accidentally changes), any changes will be realized by owner, full editor and reviewer

Originally created by @syamsoul on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3609 ### Is there an existing issue for this? - [X] I have searched the existing issues ---- ### Summary New feature that would be great to implement in Hoppscoth is: 1. New Role in Team which is `Reviewer` - `Reviewer` cannot make changes - `Reviewer` can approve/reject changes made by Editor 2. New Role in Team which is `Full Editor` - `Full Editor` can make changes - And `Full Editor` also can approve/reject changes made by Editor 3. As stated on point 1 and 2, any changes made by `Editor` must be approved by `Reviewer` or `Full Editor`. ---- So, there will be 5 roles in Team if we implement this. 1. Owner 2. Full Editor 3. Editor 4. Reviewer 5. Viewer ---- ### Why should this be worked on? - Easy to distribute tasks to team members. - Avoid mistake (accidentally changes), any changes will be realized by owner, full editor and reviewer

kerem added the

feature

label

2026-03-16 19:29:19 +03:00

kerem commented

2026-03-16 19:29:30 +03:00

Author

Owner

@liyasthomas commented on GitHub (Nov 30, 2023):

An approval system would make more sense on the source code layer.

Hoppscotch as an API tooling platform, an approval process for all changes happening to a request would make the platform cumbersome. There could be 1000's of requests and 100's of collections/folders.

@liyasthomas commented on GitHub (Nov 30, 2023): An approval system would make more sense on the source code layer. Hoppscotch as an API tooling platform, an approval process for all changes happening to a request would make the platform cumbersome. There could be 1000's of requests and 100's of collections/folders.

kerem referenced this issue

2026-03-17 00:48:27 +03:00

[PR #1247] [CLOSED] Bump babel-jest from 26.5.0 to 26.5.2 #3170