Configure Contract Management
This guide covers the Contract Management module delivered with FormKiQ Web v4.3.8. Start with a licensed Advanced or Enterprise workspace with the solution package installed. A generic workspace supplies the supporting definitions, not your organization's departments, reviewer rosters, agreement types, or workflows.
Prepare the workspace
- In Administration → Workspaces, open the intended workspace. Confirm its users, groups, permissions, and document storage configuration.
- Under Modules, enable the installed Contract Management package and refresh its configuration to install or reconcile its attribute and entity definitions. Resolve schema warnings before creating agreements; do not delete existing data to force a refresh.
- Open Contract Management's Configuration area. Configure the directories and process below before onboarding contributors.
- Configure workspace notifications and, if required, DocuSign and Document Generation. Use test recipients and a signing sandbox to validate delivery before production.
The module settings page includes an Advanced disclosure for storage/template folders, internal legal entities, ingestion, and other deployment options. Configure these for the selected workspace. Merely enabling an action does not install its backend service or grant API permission.
Departments, employees, and access
Create your departments under Configuration → Departments, then maintain employees under Employees. Use a unique, normalized email address for each person who will sign in or receive a review assignment. Employee records are directory entries: they do not create Cognito accounts, assign identity groups, or grant workspace access.
Departments have stable IDs. Archive a department to prevent new selections while retaining existing references. Review linked employees and agreement types before changing departmental assignments.
Configure contributor access in the solution's user-access settings and grant the necessary platform permissions separately. If Restrict agreement types by department is enabled, assign each employee an active department and select the allowed departments on each agreement type before enabling the restriction. Test using ordinary users from each department, including a user with no mapping.
The solution's department and user-access screens control its browser experience. They are not a substitute for backend site, document, and API authorization. In v1.19.2, do not use browser visibility as a security boundary against direct API clients. Use backend policies and, where appropriate, separate sites. See Security and folder access limitations.
Agreement types
Open Configuration → Agreement Types and define the types your organization accepts, such as Service Agreement and Non-disclosure Agreement. Configure their enabled state, process choices, and any department restrictions offered by your workspace.
Use a small test set first. Confirm that a contributor can choose an enabled type, complete its details, and start its intended review process. Retain historical mappings when disabling a type; disabling new intake does not mean existing agreements should become inaccessible.
Templates
Open Configuration → Templates. Source files are discovered in the configured template folder. Register a versioned source document as an AgreementTemplate dossier; registration links to the document rather than copying its bytes.
- Upload a supported template file into the configured folder, or use the template screen's upload controls.
- Register the source and set the template kind required by the intended generation flow.
- Inspect its current revision and required input fields. Upload a new source revision when the template changes.
- Exercise it from the matching agreement, amendment, or supplemental-document flow with fictional data. Confirm the output and document relationships before making it available to users.
- Archive obsolete templates instead of breaking references from existing agreements.
Generation requires the configured Document Generation service. A registered file is not proof that its placeholders, permissions, or generation settings are valid.
Reviewer pools and review workflows
Reviewer Pools defines named rosters, selection policies, and delegates. Create pools before referencing them from Review Workflows. Link roster entries to the employee directory where available so department and email changes have a consistent source.
For each non-business review pool, configure Backend approval groups using exact identifiers from the user's backend identity claims, one per line. Membership in any listed group satisfies that group restriction. Case and prefixes matter. A named roster assignment and a backend group are different requirements; roster membership does not grant identity-group membership.
Existing pools may display an inherited, unconfirmed approval group. Verify it against real claims, explicitly confirm or replace it, and save. Do not remove restrictions merely to unblock a reviewer. New reviews snapshot their approval groups; editing a pool does not update an existing review.
Build the review workflow in the order the business requires. Select its reviewer pools and decision behavior, then test approval, requested changes, cancellation, and resubmission. The neutral Business Owner Review is a fallback, not an organization-specific review policy. Contract Management's review configuration is distinct from the platform's generic document workflow queues.
Scheduled review delegation
Under Scheduled Review Delegation, select a review pool, original reviewer, delegate, start date, end date, and reason. Dates are inclusive. A person cannot delegate to themselves; overlapping enabled delegations for the same reviewer and pool are rejected.
Users with the appropriate write access can manage their own delegation; governance access permits managing others. The delegate still needs the workspace/document access and backend approval-group membership required for the decision. Delegation does not assign directory groups or make every existing task transferable. Test the resulting assignment for the chosen review process.
Expiry reminders
Open Expiry Reminders / Expiry Reminder Schedule, review the recipients, and save the policy. A generic workspace remains opted out until a policy is saved. Choose Business Owner and/or Agreement Owner and explicitly supply any shared Procurement or Legal mailbox you enable. Verify the notification provider separately.
At activation, the solution snapshots the effective expiry date and recipient addresses and prepares one-time reminders six, three, and one month before expiry. A valid expiry and at least one usable recipient are required for an enabled policy. The backend scheduler delivers due notifications; past occurrences are not backfilled.
Changing owners, expiry dates, defaults, or the saved policy later does not automatically reschedule existing reminders. Review existing active agreements as a separate migration. See Notifications.
Move configuration between workspaces
In Administration → Workspaces → Modules → Contract Management, use Import and export configuration to select sections, export a versioned JSON package, and preview it in a target workspace. Review additions and updates, resolve dependencies, then use Back up and apply. Refresh module settings afterward.
Imports merge selected configuration and do not delete records omitted from the file. They are a sequence of API operations, not a single transaction. After a failure, re-preview the same file to review remaining changes. Keep the downloaded target backup.
Credentials, login accounts, review delegations, agreement documents/history, allocated numbering counters, and scheduled reminder instances are not copied. Adjust environment-specific signing URLs and integrations separately. Do not enable training overrides or test-routing settings in production.
Release acceptance
Before inviting users, run the user walkthrough with an owner, an assigned reviewer, and a user who should have no agreement access. Verify generated documents, review decisions, signing order, notification recipients, lifecycle activity, and reminder scheduling. Record the Web and backend versions and the selected modules with the results.