You can now start using SPM to manage your global security policies.

The table below provides suggestions for the next steps that you can take to do this. All references relate to iManage Security Policy Manager Administration Guide.

Table: Next steps

Step

Task

Description

Section in SPM Administration Guide

1

Set up departmental security (Collections)*

Define collections based on practice area, and configure self-maintaining rules to add users automatically.

Collections

2

Apply other security policies

Apply security policies to assets in SPM.

Updating security policy section for the relevant asset type.

Refer also to User claims in iManage SPM.

3

Set user acknowledgement of security obligations

Add a memo with security instructions for the staff members of the asset, optionally withhold access until the memo is acknowledged, and configure reminders of these instructions.

<Asset> Security Memo subsection in the Updating security policy section for the relevant asset type

4

Set up security reviews

Schedule reminders to review asset security—for example, to fulfill a client's requirements.

Updating general details section for the relevant asset type

5

Manage conflicted users

Exclude conflicted users from relevant assets.

Updating conflicted users section for the relevant asset type

6

Manage team separation

Manage staffing separation across assets on multiple sides—for example, to separate teams working on opposing sides of a case, or teams working for customers that have specified exclusivity of staffing.

Managing opposing team sets

7

Assign further roles

Assign global roles, including for administrators and help desk operators.

For users that you want to have non-administrative access to iManage SPM—for example, to request access to matters—you can assign the User role.

Users and roles subsection in Getting Started with iManage Security Policy Manager

* This feature requires import of metadata. For more information, refer to Select data sources and import types.

Also refer to Optional non-scheduled import. This can be performed as and when required.