Collaborator with Sandbox-only Access
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Feature Request
Add support for assigning collaborators with “Sandbox-only” access.
Current Behavior
All collaborators currently have full project access, including production environments.
Proposed Enhancement
Introduce an access control option that allows project owners to grant collaborators access limited to specific sandboxes only (e.g., for testing or development purposes).
Benefits
- Improves security by preventing unintended production changes.
- Enables sandbox-based testing and experimentation without affecting main environments.
- Useful for QA, temporary contributors, or external testers.
Additional context
Observation: Currently all collaborators have full project access.
Suggestion: Add option to assign “Sandbox-only” access.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the collaborator access-control and sandbox permission areas, then clarify how sandbox-only collaborators should be assigned and represented. Done means collaborators can be limited to specified sandboxes without access to production environments, with coverage for the permission boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100