Nexus
Projects & Kanban

Project Access Policies

Fine-grained authorization rules controlling issue creation and deletion permissions.

To maintain security and prevent unauthorized modifications across critical work streams, each project operates under a customizable Access Policy.


Policy Modes

Project administrators (Team Leaders) can toggle between three governance levels:

Policy ModeIssue CreationIssue DeletionBest Suited For
ADMIN_ONLYTeam Leader onlyTeam Leader onlyRestricted release branches and critical system tasks
MEMBERS_CREATEAll Team MembersTeam Leader onlyStandard agile sprints requiring curated backlog cleanup
OPEN_COLLABORATIONAll Team MembersAll Team MembersHackathons, open ideation, and rapid internal testing

Enforcing Server-Side Validation

Security First Architecture

Policies are strictly enforced on both the client interface and the server layer. Even if a user bypasses UI controls, server actions re-evaluate permissions using Zod schemas and custom validation middleware before committing any changes to the database.

Changing Policy Rules

  1. Navigate to Project Settings > Security Policy.
  2. Select the desired policy from the dropdown menu.
  3. Save changes — permissions update instantly across all connected sessions.

On this page