Published

Preserve least privilege by mapping the access people and services actually have, configuring the target controls, and testing both allowed and denied actions before cutover. A successful document import does not establish that the new repository protects the same audience or permits the same operations.
Consider a legal repository where a department can read most matters, but one sensitive matter excludes several department members. Copying the department group into the target leaves the exception unresolved. The migration needs an explicit decision about that matter before its content or metadata becomes discoverable.
Identify the person or service, document scope, allowed actions, and exceptions at an agreed point in time.
Configure the destination rules and restrict records whose permissions remain unresolved.
Test representative identities and record approved differences before releasing the batch to users.
Inventory direct grants, inherited access, group nesting, explicit denials, owner privileges, service accounts, and external sharing. Preserve the source object and principal identifiers alongside the business names. A renamed group or reused email address can otherwise be mistaken for an earlier identity.
| Source concept | Target decision | Acceptance evidence |
|---|---|---|
| Repository or workspace | Choose a deployment, site, or controlled area around the required boundary. | Named owner, permitted audiences, and isolation tests. |
| Group and role | Map current identities to the necessary actions; reconcile nested membership. | Membership snapshot and separate read, change, delete, and governance results. |
| Inheritance and denial | Represent the effective restriction with supported target controls. | Allowed and excluded personas tested against descendants and exceptions. |
| Unmapped principal or exception | Keep the affected records in a restricted review population. | Unresolved scope, correction owner, and release decision. |
| External share | Re-authorise the audience, purpose, expiry, and delivery method. | Current approval and a tested plan for retiring the old link or invitation. |
FormKiQ’s security reference documents automatic and defined site permissions. In automatic mode, Finance_read grants read access to the finance site, while Finance grants read, write, and delete access. Multiple group memberships combine. Reusing a familiar name can therefore grant different actions from the source role.
Defined site permissions are available in Essentials, Advanced, and Enterprise. Folder controls require the relevant site and folder permission. Test their combined behaviour with the selected configuration. Evaluate ABAC where access depends on attributes, and govern who can change those attributes.
Document the intended privileged-access model separately. The default Admins group has full administrator access across sites. A test involving that group must reflect approved administration responsibilities; it cannot establish ordinary-user isolation.
Use an isolated target environment or an explicitly restricted site for the pilot and unresolved mappings. Limit the migration worker to its required scope and actions. Protect exports, staging files, logs, and reconciliation reports as part of the migration.
Here, quarantine describes the configured restricted population and its review process. Releasing a batch requires the agreed permission checks and an authorised decision. Configure indexing, application search scope, notifications, and any AI ingestion around that boundary. Delaying indexing alone does not restrict direct document access.
This fictional pilot migrates matter MTR-1042 from a legacy repository. Its source permits a designated reviewer, excludes another member of the legal department, and contains an unexplained historical account grant.
The team records the reviewer’s permitted actions, the excluded colleague, the matter documents and versions, and the inherited rules behind each result. The historical account remains an unresolved exception with an owner.
For this pilot, the approved design uses a separate defined site with explicit reviewer permissions and a scoped import role. It does not add the general legal-department group. The mapping records this deliberate change from the source inheritance model.
The reviewer can find and read the permitted material. The excluded colleague cannot discover the matter in the application or retrieve its document through the API. The team also checks versions, extracted text, previews, exports, and administrative paths included in the deployed solution.
The data owner investigates the historical account and records whether its grant should be removed or replaced. The matter stays restricted until that decision and the required access tests are complete. A broader department grant is not used to clear the exception.
The team captures final membership and permission changes, reruns the affected tests, and records acceptance against the batch manifest. It retires source shares under the cutover plan and retains the approved differences and rollback decision.
Check the console and API, metadata and full-text searches, previews and OCR text, relevant versions, exports, and links exposed by your application. Include connected search or retrieval applications when they receive migrated content. A denied download can coexist with a revealing title or snippet unless discovery is tested too.
Retain the identity and memberships used, source snapshot, target configuration or policy version, document scope, action, expected decision, actual result, timestamp, and reviewer. Keep sensitive content out of broadly accessible test logs. Rerun affected cases after changes to mappings, membership, classification, or policy.
If the plan revokes earlier access, include previously issued download links and already exported copies in the transition review. A target permission change alone does not prove that an old access route has stopped working.
Before cutover, test that authorised users can find and use the documents they need, and that excluded users cannot discover or retrieve restricted material. Keep unresolved records restricted. Record the results and any approved changes so the migration team can make an informed acceptance decision.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.