Skip to content

Configuration & Controls

Your organization has rules. Give them a home.

Channels, reviewers, access and legal context.

Set up the way your team captures and reviews business communications. Bring legal, compliance and technology teams into the same configuration conversation.

Configure the work your team actually does

A firm with several business lines needs more than a single archive switch. Different teams use different channels, investigate different risks and need different access. Comma brings organizational settings into a Configuration Center, with dedicated controls for connected services and review workflows.

Choose what each connection brings in

Capture settings belong close to the source. For RingCentral, for example, administrators can select calls, available call recordings, voicemail and fax. The choices depend on the connector, the source account’s permissions and the features enabled for your team.

RingCentral installation settings with separate capture controls for calls, call recordings, voicemail and fax
RingCentral capture settings. Call-recording capture depends on recordings available from the source.

Give each policy an accountable review team

Your review process should reflect who understands the risk. Comma lets you route policies into review queues and assign reviewers to those queues. Reviewers can work through flags, use saved views and connect findings with case work.

Comma reviewer inbox showing policy queues, saved views, assignment filters and flagged communications
Review queues and the reviewer inbox. Queue configuration lives alongside the team's review workflows.

Retention & Jurisdictions gives enabled teams one place to consult legal baselines and document their own policies. Each baseline includes a source citation, jurisdiction, content type and the event that starts the retention period.

Counsel can record a different interpretation and its legal basis. The catalog supports that review; it does not replace legal advice.

Configured vs. enforced

Configured means a value has been saved. Enforced means it is used by the controls operating on your data. Some entries in this workspace document policy decisions without changing those controls.

  • Counsel’s recorded interpretations document the firm’s position; they do not change the active retention schedule.
  • Policies for branches below the organization’s top-level policy record intent; those branch values do not change the schedule that runs.
  • Top-level retention settings are separate from those reference-only entries. We’ll show which controls are active in your deployment.
  • A recorded jurisdiction or cross-border policy does not move data. Data location is agreed through a separate deployment review.

Manage your compliance environment in one place

Business and personal classification settings. These controls classify captured content; they do not change what a connector captures.
Comma business and personal configuration screen with platform classifications and defaults for new contacts

The Configuration Center includes team settings, channels, contacts, classification, retention, regulatory reporting, notifications, audit, APIs and branding. A team’s role and enabled features determine what each person can see and change. Identity configuration and the jurisdiction workspace require enablement.

Team settings cover name, time zone and language. Notification settings let the team tune its delivery cadence. For FINRA-supervised firms, regulatory reporting settings collect firm identity and filing-contact information for the reporting workflow.

Retention, storage and records settings, separate from the Retention & Jurisdictions workspace.
Comma Retention, storage and records screen showing framework selection, case navigation, and outbound archive delivery settings

The Configuration Center documentation explains where administrators find each group of settings.

Start with the decisions that shape your deployment

Bring a channel inventory, your reviewer groups, identity provider, legal jurisdictions and data-location requirements. We can use those inputs to demonstrate the configuration that fits, including the boundary between a policy recorded in the product and a control operating on your data.

Frequently asked questions

Can different policies go to different reviewers?
Yes. Policies can route to different review queues, and queues have their own reviewer membership. This lets the review process reflect the responsibilities of your compliance team.
Does selecting a legal baseline make our organization compliant?
No. The catalog provides a starting point for legal review and configuration. Your organization determines its obligations with counsel. We demonstrate the controls and enforcement available for your deployment.
Do jurisdiction settings change where our data lives?
No. Recording a jurisdiction or cross-border posture is a policy decision. Data placement requires a separate deployment review covering storage, processing, backups and connector infrastructure.
Are all configuration screens available to every user?
No. Access depends on role and team enablement. Sensitive settings require administrative access, and some capabilities, including identity configuration and the jurisdiction workspace, are enabled for the deployment.

Show us how your organization works.

We'll map your channels, reviewers, legal requirements and deployment constraints to the controls you can use.

Share this page

More