The Public Content Access feature introduces a library-level privilege in iManage Control Center that gives administrators more precise, flexible control over which internal and external users can view content marked with Public or View access. It addresses a longstanding gap by allowing organizations to restrict exposure of public content to specific users within specific libraries—something that wasn't previously possible because no library-level permission model existed.

To assist you with the rollout of the Public Content Access feature, we’ve created a tool that guides you through the process of preparing your libraries for the assignment of the new privilege. This guided rollout process takes you through the feature implementation one library at a time, giving you full control at every step.

This process includes the following steps:

  • Step 1: Select a library and review whether any users are assigned to roles that don't match their user type.

NOTE: Although uncommon, mismatches can occur. For example, they can result from API imports, manual changes, or historical workarounds.

There are two scenarios to review:

  • Whether any external users are assigned to internal roles.

  • Whether any internal users are assigned to external roles.

If any users need to be reassigned to a compatible role, the process continues with Step 2. Otherwise, it continues with Step 3.

  • Step 2: If applicable, reassign affected users to roles that align with their user type. These assignments must be corrected before you enable the new privilege to ensure that no user unexpectedly gains or loses access to public content.

  • Step 3: Enable the privilege for that library and confirm that access is configured correctly.

NOTES:

  • After you enable the privilege for a library, wait at least 15 minutes to make sure everything works as expected.

  • Changes to the iManage Work Web user interface that reflect the privilege being turned on are coming soon.

  • Step 4: Repeat the process for the remaining libraries at your preferred pace.

NOTE: The deadline for completing the feature rollout is February 28, 2027. If no action is taken by that date, the system will automatically resolve any remaining mismatches by creating new roles that replicate the existing permissions with the appropriate user type. Audit reports documenting the rollout activity will be generated whether you complete the rollout manually or allow the system to complete it automatically.

This section includes the following topics: