Settings

Maximum records per entity type archived during one scheduled pass. Capped internally at 1000.

Also archives inactive users after the minimum inactive day threshold. Leave off unless user lifecycle rules are clear.

How often CMIForge checks for eligible entity records to archive.

Runs a background job that moves inactive clients and parties, closed matters, and optionally inactive users into System Archive after they have been unchanged long enough.

Records must be in an archive-eligible status and unchanged for at least this many days before the scheduled job archives them.

Display name shown in the upper-left navigation for this customer or firm.

Shows the conflict radar while users type client, matter, contact, or party names on intake forms.

Uses the configured Azure AI Search tenant index as the conflict candidate finder, while CMIForge still applies its own scoring and falls back to SQL full-text if Search is unavailable.

Runs background customer-owned data exports on a set interval and keeps recent .zip files available on Imports/Exports.

Use 0 for full exports, or enter an hour window such as 24 to export only recently changed records.

Comma-separated export data set keys. Supported values: clients, matters, parties, contacts, users, time-entries.

How many recent scheduled export .zip files CMIForge keeps before pruning older files.

How often CMIForge checks whether scheduled exports should refresh.

Safe subfolder under CMIForge scheduled-export storage. This cannot select a user's browser download folder.

Maximum form, workflow, notification, and engagement-letter history versions CMIForge keeps per definition. Form versions already used by submissions are preserved even when they are older than this cap.

Turns outbound workflow and system email notifications on or off.

Client number display pattern. Tokens: {number}, {number:6}, {year}, and {name}. Example: CL-{number:6}.

When enabled, the first matter created for a client also becomes that client's reusable matter template.

External buttons for client/matter pages. Easiest format: one line per button as Name|Url|Client,Matter. Example: Finance report|https://example.com/client/{{ClientNumber}}|Client. JSON arrays still work for advanced setup. Tokens include {{ClientNumber}}, {{ClientName}}, {{MatterNumber}}, {{MatterName}}, and {{EntityId}}.

Lets a record owner name individual viewers or editors. Normal permissions, walls, and restricted compliance access still apply.

Matter number display pattern. Tokens: {number}, {number:6}, {year}, {name}, {practice}, and {client}. Example: {year}-LIT-{number:4}.

Optional team key whose members can maintain client matter templates. Entity administrators can always maintain them.

Comma-separated fields shown in Relationship Map record previews. Options: number, type, status, email, phone.

Fallback timezone used when the browser has not provided a local timezone cookie.

Maximum rows a saved view, dashboard table, or Excel report can return for this firm. CMIForge enforces a platform ceiling of 5,000 rows.

Published form used for submissions created from inbound email.

Queues supported inbound attachments for OCR extraction once an OCR provider is configured.

Turns on Microsoft Graph mailbox polling for creating intake submissions from trusted inbound emails.

CMIForge-maintained inbound email polling diagnostic.

CMIForge-maintained inbound email polling diagnostic.

CMIForge-maintained inbound email polling diagnostic.

CMIForge-maintained inbound email polling diagnostic.

CMIForge-maintained inbound email polling diagnostic.

CMIForge-maintained inbound email polling diagnostic.

Marks mailbox messages as read after a successful CMIForge intake is created.

Hosted OpenSanctions or self-hosted yente API endpoint used for future live screening calls.

Optional full targets.simple.csv URL. Leave blank to use the dataset and bulk base URL.

Base URL for OpenSanctions bulk data snapshots.

Dataset or collection to sync, such as sanctions, default, peps, or wanted.

Hosted API, on-prem yente API, or bulk CSV sync. Use Bulk CSV for the local cache table.

Commercial OpenSanctions data delivery token. Stored server-side and hidden after save.

Turns on OpenSanctions screening configuration and sync tools for sanctions, PEP, and watchlist data.

Marks synced rows as shared CMIForge reference data. Leave off for customer-owned provider subscriptions.

Optional customer/provider account label stamped on cached screening rows for tenant-safe provider scoping.

Maximum rows to cache per manual sync run. Keep this capped while testing large datasets.

Last time a tenant administrator changed support access.

Tenant administrator who last changed support access.

Allows CMIForge support users to access this tenant for support when enabled by a tenant administrator.

Optional support-access reason supplied by the tenant administrator.

System default for time entry rounding: 0 records actual time, 6 records tenths, and 15 records quarter hours. Matters can override this.