This page provides a changelog for versions and revisions of this guide. Typically, document changes in a version reflect product changes in that version.

Changes in document version 10.4.1.0

  • The previous Monitoring page in Manage SPM is now replaced with a wholly revamped and refactored dashboard that provides you with an at-a-glance consolidated overview of system health, including the status of activity processing, agents, and imports.
    This visibility can not only help you ensure and verify the import of data and the sending of policy, but provide insight into the activity and processing loads on your iManage SPM Service. For example, if you experience a slight slowdown on a given page, but also notice a spike in system activity processing pending at that time, you can monitor that processing in near-real time and potentially avoid the need to contact iManage Support.
    For detailed information about the new monitoring page, refer to Monitoring.

  • Several items on the iManage SPM Home page have been relocated in this release. This guide has been updated accordingly. These changes are summarized in the following table.

    Table: New location of former Home page items

    Item

    New location

    Agents panels

    New Monitoring page

    Import panels (including Email Responder)

    New Monitoring page

    Activity Outliers functionality

    Settings > General Settings > Activity Feeds

  • The Activity Queue has been renamed to My Activities in this release. All previous functionality is retained. This change helps to distinguish the actions of the signed-in user from the wider-ranging System Activities displayed in the New Monitoring page. This guide is likewise updated with the updated terminology

  • iManage SPM Import now supports new-style notification events and templates. Information about this support is provided in relevant sections of this guide, for example in Settings>Notifications.

    (Generic Migration support is also available for iManage Partners.)
  • The addition and removal of assistants is now handled asynchronously by iManage SPM, freeing up user-experience-related threads. In turn, such assistant changes performed by the signed-in user are now visible in My Activities. 
  • Clarification of Settings > General > Other Links functionality. Refer to Settings > General.

Changes in document version 10.4

  • You can now set up a notification event that triggers when the security policy of an asset—that is, a client, matter, client group, or case—changes. These notifications can be used, for example, to keep the asset staffing team up to date on need-to-know status, and help provide an overview of policy changes for administrators or the conflicts team.

    • The new security policy change notifications are:

      • Security changed from Open to Restricted

      • Security changed from Restricted to Open

    As with all notification events, you can use global or local notification templates to tailor the message content and recipients as required, and a new Actioning Trustee template tag is provided to give you the option of displaying the user who performed the security change.
    This feature furthers the supersedence of old-style notification events by new-style notification events.
    Import support for this feature, which will allow bulk configuration of such notifications, is pending and will be made available in a subsequent release.
    For additional information about these new notification events, refer to Settings > Notifications, and the Updating Notifications sections for Client, Matter, Client Group, and Case.

  • Exclusionary collections let you fully exclude groups of users from a collection of matters, in a single operation.
    This feature, previously available through an early access program only, is now generally available in this release. 
    New functionalities introduced to support exclusionary collections include:
    • Option to add collection-conflicted users. 

      • When a user is added as a conflicted user on a matter, it means that they no longer have access to that matter under any circumstances, even if they have Over the Wall role, and they can't request access to the matter either. Adding such conflicted users to open matters was previously not possible at the collection level, so a group to be excluded from a group of matters would need to have been added as a conflicted group on each matter in the collection, individually. Now, however, you can add conflicted users or groups to matters grouped in collections, thereby creating 'exclusionary collections'. Bulk addition of conflicted users is also supported.
        With exclusionary collections, you can ensure that security is applied collectively to any matters in a collection—including open ones—with the conflicted users neither able to access, nor make access requests to, any matters in the collection that those users are excluded from.
        For example, if your organization's New York Office has a department within which need-to-know security isn't yet fully applied on matters, you can use an exclusionary collection to block any users from non-US regions accessing those matters. Likewise, you can use exclusionary collections for lateral hires.

      • For more information, refer to Collections and relevant subsections, including Defining Collection Conflicted Users.
    • Option to create new collections with Open security.
      • Collections can now be created with an Open security policy, to enable exclusion by way of confliction only, and without interfering with existing client or matter security, which is retained. If required, you can also add conflicted users to collections with a Restricted security policy—which will be the policy of any existing (pre-upgrade) collections. Note that collection security can't be changed, once set.
      • For more information, refer to Collections and relevant subsections, including Adding a Collection and Collections Security and Access.
    • Collection reports tab.
    • Role-related updates. 
    • Global report updates.
      • Reports updated to include collection-conflicted users, including:
        • Excluded Users report.
        • Conflicted Users report.
        • Detailed User report.
        • Policy Discrepancies report.
          For more information, refer to Generating Reports.
    • Matter Users with Access reports:
  • Updates to reflect the addition of a security policy column in the Matters tab of cases. Refer to Managing Case Matters.
  • Updates and clarifications in the Viewing User and Asset Lists and Reports pages, for Client, Matter, Client Group, and Case.
  • Further information about collection self-maintaining rule processing. Refer to Configuring Collection Self-Maintaining Rules.
  • Update of the Accessing iManage Security Policy Manager subsection of Getting Started with iManage Security Policy Manager, to include spm-cloudimanage.com-type URLs.
  • Additional clarification about (case and client group) template tags available for client and matter notification events. For more information, refer to Updating notifications sections for client and matter, respectively.
  • Information about how the values set for Import Billing Activity and Import Document Activity impact the availability and retention of such data. Refer to the Activity Feeds subsection of Settings>General.
  • Information about policy rebuilds and re-sends resulting from ID changes. Refer to the Updating General Details sections for clients, matters, client groups, cases, and collections. 

Changes in document version 10.3.4.2 - revision 1

Changes in document version 10.3.4.2 

  • New-style notification events were introduced in iManage SPM version 10.3.3, and further enhanced in subsequent versions. These are available in all applicable areas of the iManage SPM Administration Console and allow you to configure user notifications and acknowledgments in a simple and intuitive way, while freely defining their recipients and messaging. In turn, they have increasingly superseded the old-style checkbox-type notifications, to the point in recent releases where those old-style notifications have been fully superseded.
    Therefore, in this release, old-style notifications user interface elements will be removed automatically from iManage SPM, if your organization isn't using them. iManage SPM will automatically run an internal checking service weekly to see if any old-style notifications are in use:

    • If old-style notifications are in use, no changes will occur and the old-style notifications will continue to function.
    • If old-style notifications are not in use, the old-style notifications user interface elements will be removed automatically and irrevocably. 

    NOTE:

    If you are a new or onboarding customer, you will not see the deprecated old-style notifications. You can instead avail of notification events, which have stepwise creation wizards an an intuitive user interface that guides you through relevant options for each event type, including to send multiple discrete notifications for a single event, and to automate repeat acknowledgment reminders.

    For more information about notification events, refer to Changes in document version 10.3.3, Changes in document version 10.3.3 - Revision 1, and corresponding sections of this guide.

  • Clarification that basic team members can't only not action access requests, but don't receive access request notifications. For more information, refer to Adding a Client, Adding a Client Group, Adding a Matter, and Adding a Case.

  • Information about the frequency of self-maintaining rule execution. This frequency varies between asset and collection self-maintaining rules. Refer to the various Configuring Self-Maintaining Rules subsections—for example Updating Case Staffing > Configuring Self-Maintaining Rules, and Configuring Collection Self-Maintaining Rules.

Changes in document version 10.3.4.1

  • You can now quickly navigate to an asset, opposing team set, collection, or hold in iManage SPM, by pressing / (forward slash) on your keyboard, then entering that item’s ID. This updated, and more ergonomically standard, functionality complements the existing ability to access quick navigation by pressing n. You can also use quick navigate to search for clients: any partial entries are applied as filters to the client list, from where you can select the client required.
    For more information about quick navigation, refer to Understanding the interface section of Getting Started with iManage Security Policy Manager.

  • Although you can create a root path in iManage SPM Administration Console, to update the root path used by a connected agent, you need to modify the agent's CFG file—that is, editing the root path from iManage SPM Administration Console does not edit the root path sought by the agent.
    To ensure users do not misunderstand that editing a root path in the user interface would subsequently update the root path used by the agent, the root path field in Settings—which was previously an editable text field—is now non-editable. For more information, refer to Locations.

  • Scheduled awareness reminders for opposing teams sets and holds are now displayed on their own panel, aligning their presentation with that of other assets, and clearly demarcating this function from the security memo. For more information, refer to Managing Opposing Team Sets, and Holds.

Changes in document version 10.3.4

  • The new Help button 
     provides you with access to information that can help you make full use of iManage Security Policy Manager (SPM). You can discover all available features and functionalities of the user and administration consoles with explanatory overviews, detailed procedures, terminology descriptions, and contextual links. 
    For more information, refer to the Accessing the help subsection in Getting Started with iManage Security Policy Manager.

  • A series of new template tags for opposing team sets help you to easily and accurately define the content of your notifications.
    Most markedly, there's now a clear delineation between template tags that return the staffing on sides, and those that return the assets on sides, and additional, granular options for presenting both. The new template tags, in conjunction with the existing template tags for memos, recipients, and so on, ensure that you can structure and tailor corresponding notifications precisely per the requirements of your organization.
    For more information, refer to Managing Opposing Team Sets.

  • The new Administrators report, on the global Reports page, lets you download a report of all asset (that is, client, matter, client group, case) and collection administrators in iManage SPM.
    The report is sorted by users and provides useful information, including asset type and details. You can also run the report for a single user, that lists all assets that the specified user is an administrator of. You can use this—for example, to understand the administrative responsibilities of a given attorney.
    For more information, refer to Generating Reports.

  • Updated information for the Notification Email Sender Address field in Settings > Notifications. This includes domain details for this field that are required if you're using iManage SPM in the Cloud. 
  • Tip added to let you know that you can preview who'll receive a notification, by hovering over the information
    icon next to that recipient type. This preview gives you at-a-glance confirmation of the members in a particular recipient group at that moment in time. Refer to Updating Notifications sections for Client, Matter, Client Group, Case, and Holds, respectively.
  • The Notification Templates page now displays several system templates. For more information, refer to Settings > Notifications.
  • Additional information about providing feedback in iManage SPM. Refer to Providing feedback about iManage SPM.
  • Additional information to help you identify the unique identifiers of agents. This information is useful when adding included or excluded systems to iManage SPM. Refer to Adding a Matter and Getting Started with iManage Security Policy Manager.

Changes in document version 10.3.3 - Revision 1

Clarification that a simple (non-global) save of a notification event template means that that template is available only to that particular notification within the notification event, and not to additional notifications optionally added to that event. For more information, refer to:

Changes in document version 10.3.3 

  • The notifications improvements and refactoring introduced in SPM 10.3.2.x included the ability to create, edit, and save custom templates from within a notification event, including with a Save for use elsewhere option to save templates for use in other similar event types. This meant that you could have multiple globally-available notification templates, with each being further customizable as required. In this release, you can now not only manage all these saved templates from a dedicated page, but also create new global templates from a single location, without needing to edit an asset notification event.
    The new Notification Templates page allows you to quickly view, edit, or delete any saved notification event templates, from a single, bookmarkable page. For more information, refer to the Notifications Templates section of Settings > Notifications, and other sections including:

  • The Save for use elsewhere option for notification templates is now renamed to Save for global use. This change is reflected in the relevant sections of this guide.
  • The tabs where you can view historical changes, for example for audit purposes, are now renamed from History to Timeline. This change has been made where applicable, throughout iManage SPM administration console. This guide has been updated accordingly.

  • In previous version of iManage SPM, changes made in collections wouldn't trigger corresponding event notifications in affected matters. For example, if a user were added to a matter by way of collection, that user's addition wouldn't trigger a Staffing - User(s) Added notification event on the matter. This remains the default behavior, to avoid a potentially high number of notification emails when matters are added to collections with a high staffing count.
    However, if your organization wants to enable these notifications, this is now possible. For more information, refer to the Cascade collections notifications subsection in the Alerts and Notifications section of Settings > Notifications.

  • Additional information to clarify the function of the Send Reply on Completion setting, in Settings > Notifications.

Changes in document version 10.3.2.1

Changes in document version 10.3.2

  • New-style notification events are now available in all applicable areas of the iManage SPM Administration Console. These let you configure all user notifications and acknowledgements in a simpler and more intuitive way.
    You can also freely define recipients of, and compose precise messaging for, each type of notification event. Additionally, stepwise creation wizards and an improved user interface guide you through relevant options for each event type, including options to send multiple discrete notifications for a single event, and to automate repeat acknowledgement reminders. One result of these beneficial changes is that Email Templates and Email Subjects in Settings > Notifications are now superseded. For detailed information about changes in this release, refer to Service Update: iManage Security Policy Manager in the Cloud - June 2024, or for on-premises, iManage Security Policy Manager Release Notes 10.3.2.
    This document is updated throughout with relevant changes pertaining to the new functionalities introduced. Sections updated include:

  • In this release, you can view the latest features and announcements in iManage Security Policy Manager with the What's New panel. For more information, refer to Getting Started with iManage Security Policy Manager.

    NOTE:

    This feature is available only for iManage Security Policy Manager in the Cloud.

  • Additional information about Insider reports. Refer to the Insiders section in Settings > General.

Changes in document version 10.3.1.4 - Revision 2

  • Updated numerical value of the number of sides per opposing team set limit. For more information, refer to Managing Opposing Team Sets.

Changes in document version 10.3.1.4 - Revision 1

  • Added numerical values of the limits introduced in SPM 10.3.1.4 to improve the performance and stability of opposing team set creation and processing. For more information, refer to Managing Opposing Team Sets.

Changes in document version 10.3.1.4

  • The Notifications Settings pane in the Alerts and Notifications tab is now refactored for greater clarity and ease of use. Improvements include:

    • Clearer options and friendly pop-ups to help guide you to successful setup and avoid invalid configurations.
    • Separation of Access Request Notifications and Security Memo Notifications settings from the Enable Incoming Email Mailbox Monitoring setting. Previously, the Enable Incoming Email Mailbox Monitoring settings had to be toggled on to see all of the methods for approvals and acknowledgements, including those not requiring mailbox monitoring, such as Link to User Console.
    • The Reply-to Notification Email Settings are now renamed to Incoming Email, and are now only visible when the Incoming Email check box is selected. This makes for a simpler and less cluttered experience. Additionally, when Reply to Notification Email is selected for access requests or security memos, a message displays indicating that the Incoming Email settings will be used in that case.
      For more more information, refer to Notifications.

  • Previously, the Bulk Add Members and Bulk Add Custodians options were only accessible through an ellipsis

    button. In this release, these options are clearly visible on new split buttons for Add Members and Add Custodians, respectively. In addition to providing better visibility of these options, this change also reduces click count and streamlines workflow.
    This guide is updated, where applicable, to reflect these changes.

  • A number of limits have been introduced in SPM to improve the performance and stability of opposing team set creation and processing. For more information, refer to Managing Opposing Team Sets.

Changes in document version 10.3.1.3

  • You can now pin individual filters at the page level in the iManage SPM administration console. Pinned filters are applied across similar pages of a given asset type. For example, filters pinned on the staffing page of a matter are applied across the staffing pages of all matters. The filters that you pin are retained within the browser you are using and between sessions on a given device. This lets you retain specific, customized views of asset pages or other page types as required whether using the administration console in a single tab or across multiple tabs. For more information, refer to:

  • Format of iManage Work at cloudimanage.com links that you can use to add iManage Work documents or folder hyperlinks in security memos, notes field, and 'text' custom properties. For more information, refer to iManage Work document and folder links section in Settings.
  • Additional information about SPM client and server version, applicable to iManage Security Policy Manager (SPM) in the cloud users. Refer to Viewing the version of SPM in Getting Started with iManage Security Policy Manager.

Changes in document version 10.3.1.2

  • The Home page now includes a Collections count in the overview panel. For more information, refer to Home Page.
  • Canadian French is now included as a default language in iManage Security Policy Manager (SPM). When selected, visible and interactive elements in SPM Administration Console and SPM User Console, including notifications, reports, and error messages, are displayed in Canadian French. For more information, refer to the Language section of Settings>General.

  • iManage Security Policy Manager (SPM) Administration Console has many improvements that make it easier for you to view, or search for, clients in a client group.
    Firstly, clients in a client group can now be viewed directly in the clients list, without needing to browse to the client group itself. They can be viewed as clients in the clients list (they're no longer hidden within their client group; and as selectable tooltips, when the new View Clients option is selected under the client group. Refer to:

  • You can now add a reason when acknowledging a security memo on behalf of another user. Any reasons entered are preserved, and can be viewed in the history (audit) tab of the relevant asset. They're also available in the new AcknoAcknowledged on behalf of reportwledged on behalf of report. Refer to, for example:
  • Clarification of matter security options, both in terms of how they relate to the parent asset's security, and how parent asset security affects availability of users for the matter staffing team. For more information, refer to Adding a Matter and Updating Matter Security.

Changes in document version 10.3.1.1

  • You can now add matters directly from the new (in version 10.3.1) Matters page, using + Add Matter. For more information, refer to Adding a Matter.

  • Security policy wording in the iManage SPM Administration Console has been updated for improved clarity and inter-product consistency. These changes are reflected in the documentation where applicable, and include:

    • Updated descriptions of security policies in the Policy panel of assets, for clarity.
    • Labeling of the security policy of matters restricted by a case is now "Restricted by case," rather than "Restricted".
    • "Restricted" client security policy now has a single check box labeled "The staffing of Matters that are changed to Restricted is limited to users named under Client staffing," in place of the two radio buttons "Can only be more restrictive than client staffing" (equivalent to new check box selected) and "Can open up access to users not in client staffing" (equivalent to new check box not selected).
      In this guide, these changes are reflected where required, including:
      • "More restrictive than <asset> staffing" is now changed to "Limited to users named under <asset> staffing".
      • "Can open up access to users not in <asset> staffing" is now changed to "Not limited to users named under <asset> staffing".
    • Renaming of the "Security Policy" panel, in the Security tab of assets, to "Policy".
  • Notification Events have now moved from the Security and Conflicted Users tabs of assets, to the Notifications tab of assets. This means you can now create and manage notification events from a single location. For more information, refer to the Updating Notifications sections (for clients, client groups, matters, and cases).
  • Updated the information on bulk addition using semicolon-separated lists. Refer to Filters.

Changes in document version 10.3.1

  • In previous versions of iManage SPM, matters were only accessible under their clients, client groups, cases, or collections. In this release, a new Matters page provides flat-list viewing, filtering, and searching of all matters being administered by iManage SPM, regardless of their parent asset type. The Matters page is available separately on the navigation bar, and includes the main functionality of matter lists available on other pages. This document has been updated to reflect these changes.

  • You can now add conflicted user information to notification emails, using the new conflicted user template tags, which also provide flexible presentation options. Refer to—for example, Notifications.

  • Changes to reflect new groupings of template tags for simplicity and ease of use, and removal of template tag monikers. Refer to—for example, Notifications.
  • Opposing team set reports now contain additional information that provides you and/or your compliance team with greater insight into any information barriers in place. Refer to Generating Reports.

  • In previous versions of iManage SPM, you could configure the iManage SPM agent for Microsoft Teams to ignore (allow) specified external domains, so that users from those domains wouldn't be subject to policy processing by the agent. In this release, you can allow users from such domains on a per-location and per-asset basis, providing additional flexibility when collaborating with external users. External domains for Microsoft Teams can also now be specified in the iManage SPM Administration Console (rather than the agent CFG file). Global domains locations can be set to allow users from external domains, and this can be overridden at the matter level; matter-level locations can also be set to allow users from external domains. For both location types, a check box defines whether such users are allowed (checked) or subject to policy processing (unchecked).
    For more information, refer to:

  • Orthographical updates and other fixes.

Changes in document version 10.3.0.1

  • In previous versions of iManage SPM, matters that were secured by a client (that is, restricted by a client with 'more restrictive' matter security) weren't visible in the Add Matter dialog for cases because secured-by-client matters can't be added to a case. This meant, however, that to add this type of matter to a case, you had to go back to the matter's client and adjust the client security there. In turn, this had to be done for the clients of all such matters.
    In this version of iManage SPM, the Add Matter dialog box now shows these matters, and if you want to add them to the case, provides the option of modifying their (parent) client security from 'More restrictive' to 'Open up'. When this option is selected, the client's security is adjusted, and the matter is added to the case. Bulk addition—and bulk security modification—is also supported. This new functionality greatly reduces the number of steps required to perform this type of operation, thereby providing time savings for your risk and compliance teams.
    For more information about this feature, refer to:

  • When plain text is entered in a text filter, corresponding characters with diacritics are now returned. Refer to Filters.

  • When editing an email template, you can view that template's email subject in the preview panel—for example, refer to Notifications.

  • You can now view the templates used for notifications and notification reminders, in the notification events panel. More more information, refer to the Updating Security Policy sections for Client, Client Group, Matter, and Case.

Changes in document version 10.3

  • In this version of iManage SPM, members of the conflicts team can now permit individual users, such as specialists, to access all sides of an opposing team set without triggering exclusions. The new Opposing Team Set Floating Users functionality lets you specify these users on a per opposing team set basis. It also ensures that users are permitted access across specified opposing team sets only, without needing to be granted a higher role that could provide unnecessary access to other items.
    For more information about this 'local' floating users option, refer to:
  • When adding items to an asset in iManage SPM Administration Console, for example adding matters to an opposing team set side, or clients to a client group, you can now use a semicolon-separated list as a filter for the required assets, enabling one-click addition of multiple targeted assets. This not only saves time but prevents selection errors. For more information about this feature, refer to Filters.
  • Notification Events let you configure user notifications and acknowledgements in a simpler and more intuitive way. The new stepwise creation wizard helps you create precisely the notification event types required, while also simplifying acknowledgement and reminder setup. Refer to the Updating Security Policy subsections in the Clients, Matters, Client Groups, and Cases sections.
  • Flexible presentation of users in email notifications: you can now simplify how users, including allowed users and users on opposing team set sides, are presented in notification emails. Refer to Settings > Notifications, and the Updating Security Policy subsections in the Clients, Matters, Client Groups, and Cases sections.
  • Option to generate and download a report showing opposing team sets across all clients and matters. This enables you to, for example, obtain a complete summary of all ethical walls implemented in your organization. Refer to Generating Reports.

Changes in document version 10.2.4

(Changes since document version 10.2.3.)

  • Permissions updates that prevent staffing administrators from adding excluded users to assets— for example, refer to Global Roles Task Mapping in Users and Roles.
  • Re-authorize SPM when required. Refer to the Authorization section in Settings > General.
  • Specify the display timezone of notifications sent by SPM (and regardless of the timezone that the SPM server is in). Refer to the Alerts and Notifications section in Settings > Notifications.
  • Require users to acknowledge their addition to a side of an opposing team set. You can use this feature, for example, in conjunction with the opposing team set security memo to ensure attorneys understand and acknowledge their responsibilities when added to ethical walls. Refer to Managing Opposing Team Sets.
  • Define whether the assistants of timekeepers with a conflict of interest on an asset are prevented from accessing workspace content. This gives you further flexibility to fulfill client and matter partner requests about assistant access. For more information, refer to Settings > General and Managing Assistants.
  • Updated creation wizards for Clients, Matters, Client Groups, and Cases.