admin-workflows

ArtisanClarinets's avatarfrom ArtisanClarinets

Administrative tasks, RBAC hierarchy, and business workflows.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[SOPs and Playbooks]

When & Why to Use This Skill

The Admin Workflows skill is designed to optimize organizational efficiency by documenting and automating core administrative processes. It features a robust Role-Based Access Control (RBAC) hierarchy for secure access management, seamless transitions from proposals to projects, and structured lead management. Additionally, it incorporates mandatory audit logging for privileged actions, making it an essential tool for maintaining operational transparency and security compliance within business platforms.

Use Cases

  • RBAC Implementation: Defining and enforcing hierarchical access levels (Owner, Admin, Editor, Analyst) to ensure secure data management and clear accountability.
  • Project Lifecycle Automation: Streamlining operations by automatically converting approved business proposals into active projects while preserving budget and client details.
  • Sales Pipeline Management: Standardizing the lead management flow from initial contact through qualification to final conversion status.
  • Security and Compliance Auditing: Automatically tracking and logging all privileged administrative mutations to maintain a comprehensive audit trail for system integrity.
nameadmin-workflows
descriptionAdministrative tasks, RBAC hierarchy, and business workflows.

Admin Workflows

This skill documents high-level administrative processes.

RBAC Hierarchy

The system enforces the following role hierarchy:

  1. Owner: Full system access, can manage billing and structural configurations.
  2. Admin: Can manage users, projects, and settings within a Tenant.
  3. Editor: Can create and modify content (Projects, Contracts).
  4. Analyst: Read-only access to data and reports.

Core Workflows

1. Proposal -> Project

  • Trigger: A "Proposal" is approved.
  • Action: The system converts the Proposal object into a generic "Project".
  • Data: Carries over budget, timeline, and client details.

2. Lead Management

  • Flow: Inbox -> Status Update.
  • States: New, Contacted, Qualified, Proposal Sent, Won/Lost.

3. Audit Logging

  • Requirement: All privileged actions must be logged.
  • Scope: Any mutation by an Admin or Owner (e.g., changing user roles, deleting projects).
  • Storage: AuditLog table (via Prisma).