indigo
db2c414c1a
Users can now hold multiple roles, each with its own editable set of create/edit/delete-style permissions across assets, shots, tasks, task assignment, review approve/retake, submissions, uploads, and notes (including internal vs. client note visibility). The 4 existing roles (coordinator/director/artist/developer) are migrated into the new system as system roles, seeded to reproduce today's actual behavior exactly; admins can create custom roles (e.g. "Reviewer", "Outsourcing") via the new Role Management page and assign multiple roles to a user via a new "Manage Roles" action on the Team page. Backend: - New Role/Permission models and role_permissions/user_roles tables, plus a one-off, idempotent seed/backfill migration script. - New require_permission()/user_has_permission() dependency, wired into the actual mutation endpoints across shots/assets/tasks/reviews, always preserving existing ownership- and self-service-based access (e.g. artists editing their own task status, own notes, own uploads, own submissions) as an unconditional fallback alongside the new permission checks - nothing that worked before now requires a role. - New endpoints: PUT/DELETE on task submissions (wires up soft-deletion columns that existed on the model but were never exposed), plus full role CRUD and per-user role assignment. - Along the way: fixed newly-created users not being linked to their matching system role (silently leaving them with zero permissions), and unified an inconsistency between the single vs. bulk task status endpoints that allowed different roles to bulk-update status. Frontend: - Role Management page with a grouped, human-readable permission editor (icons, plain-language action labels, per-resource select-all, live selected count) replacing an earlier dense matrix prototype. - hasPermission() added to the existing usePermission() composable without touching its current isAdmin/isCoordinatorOrAdmin consumers. - Note composer gets an Internal/Client toggle; submissions gain inline edit/delete actions gated the same ownership-or-permission way as notes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
42 lines
1.5 KiB
Python
42 lines
1.5 KiB
Python
# Models package
|
|
from .user import User, UserRole, DepartmentRole
|
|
from .project import Project, ProjectMember, ProjectStatus
|
|
from .episode import Episode, EpisodeStatus
|
|
from .asset import Asset, AssetCategory, AssetStatus
|
|
from .shot import Shot, ShotStatus
|
|
from .task import (
|
|
Task, Submission, Review, ProductionNote, TaskAttachment,
|
|
TaskType, TaskStatus, ReviewDecision, AttachmentType, NoteType
|
|
)
|
|
from .api_key import APIKey, APIKeyScope
|
|
from .api_key_usage import APIKeyUsage
|
|
from .global_settings import GlobalSettings
|
|
from .notification import Notification, UserNotificationPreference, NotificationType
|
|
from .activity import Activity, ActivityType
|
|
from .role import Role, Permission, role_permissions, user_roles
|
|
|
|
__all__ = [
|
|
# User models
|
|
"User", "UserRole", "DepartmentRole",
|
|
# Project models
|
|
"Project", "ProjectMember", "ProjectStatus",
|
|
# Episode models
|
|
"Episode", "EpisodeStatus",
|
|
# Asset models
|
|
"Asset", "AssetCategory", "AssetStatus",
|
|
# Shot models
|
|
"Shot", "ShotStatus",
|
|
# Task models
|
|
"Task", "Submission", "Review", "ProductionNote", "TaskAttachment",
|
|
"TaskType", "TaskStatus", "ReviewDecision", "AttachmentType", "NoteType",
|
|
# API Key models
|
|
"APIKey", "APIKeyScope", "APIKeyUsage",
|
|
# Global Settings models
|
|
"GlobalSettings",
|
|
# Notification models
|
|
"Notification", "UserNotificationPreference", "NotificationType",
|
|
# Activity models
|
|
"Activity", "ActivityType",
|
|
# Role models
|
|
"Role", "Permission", "role_permissions", "user_roles"
|
|
] |