Skip to content
Probo
Get compliant

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

Get started

Product

Deployment

Developers

Try searching for

Tab to move through results · Enter to open · Esc to close

prb consent-record command reference

Reference for 3 commands under prb consent-record, including usage, flag types and defaults, required flags, source examples, and implementation links

View as Markdown

Manage cookie consent records. This page documents 3 commands under prb consent-record.

Flags and examples below come from the command definitions. A Required flag is explicitly marked required by Cobra; an unmarked flag can still be needed by runtime validation or a non-interactive workflow. Empty strings and empty lists are registered defaults, not sample values.

Every command also inherits the global flags. Run prb <command> --help to check your installed version. Replace placeholder IDs and names in source examples before running them. Return to the complete CLI command reference to browse another command.

Commands

Section titled “Commands”
CommandDescriptionUsageSource
prb consent-recordManage cookie consent records.prb consent-record <command>View implementation
prb consent-record listList cookie consent records for a banner.prb consent-record listView implementation
prb consent-record viewView a consent record.prb consent-record view <id>View implementation
Section titled “prb consent-record”

Manage cookie consent records.

Usage

Section titled “Usage”
prb consent-record <command>

View command implementation.

Section titled “prb consent-record list”

List cookie consent records for a banner.

Usage

Section titled “Usage”
prb consent-record list

Accepts no positional arguments.

Flags

Section titled “Flags”
FlagTypeDefaultRequiredDescription
--actionstring""—Filter by action
--afterstring""—Cursor from the previous page (the Next cursor line)
--banner-idstring""RequiredCookie banner ID (required)
--jsonbooleanfalse—Output JSON (same as —output json)
--limit, -Linteger30—Maximum number of items
--output, -ostring""—Output format: json, table (default)
--versioninteger0—Filter by version
--visitor-idstring""—Filter by visitor ID

View command implementation.

Section titled “prb consent-record view”

View a consent record.

Usage

Section titled “Usage”
prb consent-record view <id>

Requires 1 positional argument.

Flags

Section titled “Flags”
FlagTypeDefaultRequiredDescription
--jsonbooleanfalse—Output JSON (same as —output json)
--output, -ostring""—Output format: json, table (default)

View command implementation.