8000 Policy Approval Workflow · Issue #510 · trycompai/comp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Policy Approval Workflow #510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to 8000 your account

Jump to bottom
Closed
linear bot opened this issue May 2, 2025 · 1 comment
Closed

Policy Approval Workflow #510

linear bot opened this issue May 2, 2025 · 1 comment
Assignees
@Marfuen
Labels
Feature

Comments

@linear
Copy link
linear bot commented May 2, 2025

Goal

Introduce a lightweight Policy Review & Approval workflow that routes each draft to an assigned approver, captures a formal approve / reject decision, and enforces that an approver is named whenever the policy’s Require Signature toggle is on.

UI / Workflow

  1. Policy Detail (Draft) → creator clicks Submit for Approval → modal opens with Approver dropdown (searchable list). If Require Signature is on, Approver is marked “required” and the Submit button stays disabled until a user is chosen.
  2. Approver receives notification; selects item in Approval Inbox or linked directly from email → reads policy → chooses Approve or Reject, adds mandatory comment, confirms.
  3. Approve → policy status flips to Active, banner shows “Published - awaiting employee acknowledgments.”
  4. Reject → modal closes, policy returns to Draft; editors see rejection badge and the approver’s comment at top of page.
  5. Creator revises content and can resubmit as needed.

Key Functionality

  1. Submit for Approval button appears on any Draft Policy
  2. Creator must pick exactly one approver; if the Require Signature toggle is enabled, the approver field becomes mandatory and the form cannot be submitted until an assignee is selected.
  3. Creating an approval record sends an email or in-app notification to the chosen approver and places the item in their Approval Inbox.
  4. Approver can Approve or Reject and has the option to leave a comment; decision and comment are stored with timestamp and user ID.
  5. Approval sets policy status to Active, publishes it to employees, and triggers the acknowledgment/signature cycle (if employee signature is required); rejection returns policy to Draft with the comment visible to editors.
  6. Can we have all approval actions write immutable entries to the Audit Log?
  7. Generate a history record in the policy’s Version History
  8. Admins may reassign the approver before a decision is made; reassignment notifies both old and new approvers.

Acceptance Criteria

  1. Attempting to submit a Draft with Require Signature toggled on but no approver selected disables Submit and shows inline validation.
  2. Approver decision posts to Audit Log and appears in Version History with exact comment text.
  3. Approving a policy fires the acknowledgment workflow and sends emails to employees.
  4. Rejecting a policy changes its status back to Draft, preserves version number, and displays rejection comment to editors on first load.
  5. Reassigning an approver before decision logs both the reassignment and the final decision as separate Audit entries.
@linear linear bot added the Feature label May 2, 2025
@linear Linear
Copy link
Author
linear bot commented May 2, 2025

COMP-114 Policy Approval Workflow

@Marfuen Marfuen self-assigned this May 15, 2025
@Marfuen Marfuen closed this as completed May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Marfuen Marfuen

Labels
Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Marfuen
0