Feature Request: Read-Only Access for Server/Bench/Sites
- Dominant language
- Python
- Stars
- 562
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
Hi Team,
We have a requirement where we need to provide read-only access to some users for monitoring purposes. At present, even if we configure permissions, the access still allows both read and write, which creates a risk.
Our use case is:
Users should be able to only view a specific server, its bench, and the sites hosted on it.
They should not be able to perform any actions like creating, deleting, or modifying sites/benches.
The access should be strictly view-only.
This feature is important when we want to give external team members or clients visibility without allowing them to make changes. It will help avoid accidental modifications and keep the environment secure while still enabling collaboration.
Could you please consider adding this as a feature?
Thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating how permissions are applied to servers, benches, and sites, then determine the design needed to enforce view-only access. Done means users can inspect the specified resources but cannot create, delete, or modify them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100