Introduction

Matter Security Introduction

With matter security, administrators have the ability to configure access to matters based on user roles and explicit allow/deny lists. Changing a matter's access will affect whether or not specific users can see them within Agility Blue, including any items that are directly association with them. This can be useful in a variety of scenarios, such as information barriers where specific users should not be able to view matters due to need to know, conflicts, or contractual obligations; or portal request scenarios where you would like your portal users to select matters that only pertain to them. To facilitate these types of scenarios, there are 2 new areas that can be used to configure matter access: The roles settings on the permissions section of the workspace settings page and the security tab on any matter settings page.

Permissions

You will need to be an organization administrator or belong to a permissions group that grants view rights to the matter security permission in order to configure matter security. The workspace administrators permissions group has this setting enabled by default, but all other permissions groups do not have this permission granted. Note that the permissions group will need to have the "Settings" permission granted in order to grant the "Security" permission.

Effects of not having access to a matter

Users that do not have access to a matter have the following effects:

• The user cannot see the matter in the matter grid views, matter details page, and it will not show up in searches.

• Any projects related to the matter will not be visible.

• Any tasks related to the matter will not be visible. This also affects items directly associated with tasks such as comments and emails.

• Any billing entries that are associated with the matter, either directly with the matter or from a descendant project/task, will not be visible.

• Any media log entries that are associated with the matter, either directly with the matter or from a descendant project/task, will not be visible.

• Any volumes that are associated with the matter, either directly with the matter or from a descendant project/task, will not be visible.

• Any attachments that are associated with the matter, either directly with the matter or from a descendant project/task, will not be visible.

• If the user has permissions to run reports the user may see information about matters that they don't have access to within the app.

• Any custom object that references a matter will still show that reference within the grid that contains the matter name and matter reference id. However, if the user tries to view more details about the referenced matter, they will be presented with a "not found" error.

• Members of the organization administrator role have access to all matters and are not affected by matter security settings.