Quick answers
Frequently asked questions
The short version, for when you need the answer and not a small novel.
Teams group users for workflow assignment, visibility, and approval routing. Security roles grant capabilities such as viewing entities, designing forms, reviewing conflicts, or administering the system.
A team can carry one or more roles, and a user can also receive roles directly. Keep the two concepts separate so workflow membership does not accidentally become broad system access.
CMIForge finds exact, normalized, fuzzy, alias, role, relationship, and sanctions-related matches. It explains why each result appeared and can summarize the review set.
A qualified reviewer still clears, escalates, or records the conflict decision. AI assists the review; it does not silently approve a matter.
In Design Studio, map a form field to the client, matter, party, contact, or user field it represents. CMIForge keeps the durable field identifier behind the scenes, so labels can change without breaking the relationship.
Mapped values can be saved during conversion or by a workflow outcome configured to save entity fields. Approval-driven saves retain an audit trail.
Start with the published intake form your firm uses for that type of work. The submission detail page then becomes the workspace for review, conflicts, workflow actions, document generation, and conversion into clients or matters.
If you are unsure which form applies, ask your CMIForge administrator before creating a second request.
Use the Reports area to run available operational, intake, conflict, workflow, entity, and time reports. PDF reports include the configured firm name and can be previewed before download. Data-heavy reports may also offer CSV output for analysis.
A strong support question includes the CMIForge page or feature, the steps you took, the result you expected, what happened instead, and any visible error message. Screenshots are useful when they do not contain confidential information.
Never post client secrets, access tokens, passwords, connection strings, or privileged matter details in the community portal.
Engagement letters are reusable Design Studio templates, separate from a single workflow. Add supported CMIForge variables to the free-text body, configure the letterhead, and select the template from an Engagement Letter step.
Workflow routing rules can choose different paths and templates. Generated letters can be produced as Word or PDF documents.
Open the form in Design Studio and check the field's Access and Workflow settings. Fields may be Editable, Read only, or Editable in selected steps.
For selected-step editing, the workflow and version must match the form's assigned workflow. If no exact version match exists, CMIForge shows the available workflow steps so the setup can still be corrected.