Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Compliance Controls Settings Block for React

A policy review window: a rail of six sample policies grouped Overdue, Due soon and Current, and a pane with owner, cadence, the next review worked out from a typed date and who has acknowledged.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Keep a company's policies reviewed on time, with this compliance controls window for React with Base UI. It is a fixed-height window with its own top bar and two panes. The rail lists six sample policies (access control, incident response, data retention, vendor review, acceptable use, change management) in three groups, Overdue, Due soon and Current, each row saying when its next review falls ("Overdue by 12 days"). The pane has an owner Native Select, a review cadence in a Segment Group (6 or 12 months), the day it was last reviewed, the next review worked out from the two, the frameworks it serves (SOC 2, ISO 27001, HIPAA, GDPR) as Badges and how many of 42 members have acknowledged it, with a Remind button for the rest. The top bar's one Shine Button, Mark reviewed, sets the last review to a typed date and the rail sorts itself again, so a policy moves from Overdue to Current; changing the cadence moves it too. These are samples: nothing here is legal advice, and marking a policy reviewed certifies nothing. On a phone the rail and the chosen policy are one pane at a time with a Back button. It's built from Native Select, Segment Group, Badge, Button, Shine Button and Guides, with a CSS entrance only. For a compliance tool, a security dashboard or any product that tracks policy reviews.

FAQ

How do I add a policy or change the dates?

Edit START: each policy has a name, its last-reviewed day (ISO), the cadence in months, an owner from OWNERS, the frameworks it serves and how many members have acknowledged it. The next review is the last review plus the cadence, with the day pulled back to the month's last day when the month is shorter, and everything is measured from the typed AS_OF date in UTC, so the words never follow the clock. The rail groups are derived: overdue before that date, due soon within 30 days of it, current after.

What does Mark reviewed do?

It sets the chosen policy's last review to the typed date. Its next review moves a cadence on, the policy moves to the Current group, the rail sorts itself again and the status line at the foot says when the next review falls and which group it is in, adding that nothing is certified. Focus stays on the button, so you can choose the next policy and mark that too.

What happens when I change the cadence?

The next review is worked out again from the last one: switching an annual policy to six months can make it overdue at once, and the other way can make an overdue policy current. The rail and the badge follow, and the status line says where the policy stands now.

What stays local, and how do I make it real?

Everything, and nothing is sent: owners, cadence, reviews and reminders live in this page's state and return to their starting values on reload. Remind queues nothing and says so. To make it real, store the policies and the acknowledgements with your account, send the reminder through your mail service and record who marked a policy reviewed and when; certifications come from an auditor, never from this button.

How does it work by keyboard and on a phone?

Each policy in the rail is a real button marked as current; choosing one moves focus to its name when the rail is hidden. On a phone the window keeps its height and shows one pane at a time: the rail first, then the policy under a Back button that returns to the row you left, with Mark reviewed shown only while a policy is open. The status line is a polite live region present from the start.

  • Pro

    GDPR Consent Settings

    Privacy and consent

    A purposes register with a legal basis, retention and consent record per purpose, a rule that withdrawing must be as easy as giving, and three data requests counted down from 30 days.

  • Pro

    Data Classification Settings

    Privacy and consent

    A four-label ladder (Public, Internal, Confidential, Restricted) as columns of handling switches, with six sample documents whose label is checked against what it requires.

  • Pro

    Audit Log Retention Settings

    Backups and exports

    An audit log retention panel with a row for each class of event, a preset for how long to keep it, an archive-after menu, a legal hold that freezes the row and a two-part bar to one scale, with the gigabytes searchable and archived added up from typed daily volumes.

  • Pro

    A clinic compliance workspace's setup step as a whole screen: frameworks as tabs that show how many of four sample requirements are done, rows with a checkbox, a line of evidence and an owner, a progress line that follows the tab, and Mark all complete with Undo.

  • Pro

    A roles window with a rail of five roles and a detail of grouped permissions: mixed-state group boxes, a Compare with select that marks each permission with a plus or a minus, read-only system roles and Duplicate to edit.

  • Pro

    Cookie Consent Settings

    Privacy and consent

    A cookie preferences page with four purpose cells on shared hairlines: necessary locked on in words, three switches, and under each the exact cookies it covers, kept for how long, set or blocked.