brain/wiki/platform-editions-ee/ee-projects-rbac.md
The EE Projects module adds team collaboration, role-based access control, git-based environment sync, and per-project piece filtering on top of the base project. CE is single-user only; EE gates the feature set behind projectRolesEnabled and environmentsEnabled plan flags.
(projectId, userId, projectRoleId, platformId), unique on (projectId, userId, platformId). Service: upsert, list, getRole (returns ADMIN if owner/platform admin), update, delete, getIdsOfProjects.type DEFAULT/CUSTOM. Built-in: ADMIN (all 26 permissions), EDITOR (read + write flows/folders/tables, update flow status), VIEWER (read-only). Custom roles behind customRolesEnabled.READ_FLOW, WRITE_CONNECTION, etc.).Yes, RBAC is a middleware layer. rbacMiddleware is registered once as a Fastify preHandler in app.ts, so every route passes through it. It resolves the route's project + permission and delegates to rbacService, which routes by principal type: USER goes to the member's role permission check; ENGINE checks principal.projectId === requestedProjectId; SERVICE checks project.platformId === principal.platform.id. UNKNOWN, WORKER and ONBOARDING are rejected outright.
The service method is spelled assertPrinicpalAccessToProject(), with the typo, in the code. Grep that spelling, not the corrected one, or you get zero hits. Flow-level checks use a separate assertUserHasPermissionToFlow().
Note it lives under ee/authentication/, not ee/projects/, which is where most people look first.
type GIT_BRANCH/MANUAL/ROLLBACK. Workflow: releasePlan() computes a ProjectSyncPlan diff (including exact piece version changes), create() applies + serializes to a File. Memory lock prevents concurrent releases.project.pieceSetId (nullable FK, SET NULL). When managePiecesEnabled, new EE projects get the Default set on create; unassigned resolves to Default at filter time. This supersedes the legacy project-plan allow/block list.workerGroupId (bare label, ^[a-z0-9_-]+$) gated by workerGroupsEnabled. When set, the project's EXECUTE_FLOW/EXECUTE_WEBHOOK jobs route to project-<label>-jobs; other job types unaffected. Set via POST /v1/projects/:id; GET /v1/projects/worker-groups (platform-admin) lists online project-scope workers, 402 when flag off.platformProjectService.getForPlatform(): admins see all, operators see all except others' personal, users see own personal + team projects they're a member of.Entry point: rbacMiddleware, registered as a preHandler hook in app.ts.
packages/server/api/src/app/ee/authentication/project-role/ — where RBAC actually lives: rbac-middleware.ts and rbac-service.tspackages/server/api/src/app/ee/projects/ — the projects module; members, roles and releases all sit under itpackages/server/api/src/app/ee/projects/project-members/ — member CRUD, role lookuppackages/server/api/src/app/ee/projects/project-role/ — built-in and custom rolespackages/server/api/src/app/ee/projects/project-release/ — release create, diff, applypackages/server/api/src/app/ee/projects/project-release/git-sync/ — SSH repo push/pullpackages/server/api/src/app/core/security/v2/authz/ — calls into rbacService from the authz layerpackages/core/shared/src/lib/ee/project-members/ — ProjectMember typespackages/core/shared/src/lib/automation/project-release/ — ProjectRelease, ProjectSyncPlanpackages/web/src/features/members/ — members UIpackages/web/src/features/project-releases/ — releases + git sync UIPaths verified 2026-07-17. An earlier version of this list pointed at ee/project-members/, ee/project-role/, ee/project-release/ and ee/git-sync/; all four moved under ee/projects/.