feat(ep): restrict resource-creation endpoints to admin emails only#331
Merged
Conversation
POST /api/v1/projects, /workspaces, /teams, and clone routes now require the requesting user to be in ADMIN_EMAILS, using the existing adminOnly middleware.
Project endpoints remain open for EP provisioned users who need to create and manage projects themselves.
field123
approved these changes
May 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this MR do?
Restricts workspace and team creation to users listed in `ADMIN_EMAILS` only, using the existing `adminOnly` middleware. Project endpoints remain open — EP provisioned users need to create and manage projects themselves.
Changes
Design decisions
`adminOnly` was chosen over a new email-domain guard because admin identity is already defined by the `ADMIN_EMAILS` env var and used consistently for all `/api/v1/admin/*` routes. No schema changes or new config is needed.
Testing
Manually verify: a non-admin session hitting `POST /api/v1/teams` or `POST /api/v1/workspaces` should receive `403 Forbidden`; an admin session should succeed as before. Project creation endpoints should be unaffected for all authenticated users.