Administration > Manage

Manage

Node Description
Service Agents

This node is used to register service agents (WebServer and WindowService), configure agent jobs for the agents, and assign them to processors.

Note: For any new Service Agents added, the Agent Jobs is not enabled by default. The Administrator must manually enable Agent Jobs when adding a new Service Agent.

Global Settings This node is used to manage application-level properties. This includes showing and ordering modules and tabs, sending notifications, setting SMTP/IMAP settings, logs and maintenance, profitability and Jackson reports, and matter view options.
User Preferences

This node is used to manage user settings. The following options can be configured:

  • Localization Settings : You can determine what regional/cultural settings are to be applied within Umbria.
  • Exchange Settings: Select the Sync Exchange Contacts checkbox and click Save to sync, contacts from your Microsoft Exchange account into the My Contacts section of Umbria's Experience and Relationships module.
  • Matter Planning Preferences: Configure options related to matter planning and budgeting. This determines how various fields default.
  • Template: Add customized budget templates. To create a new template, click the Add Template button in the upper right corner of the screen.
  • Since Inception Report Settings: Select the Show Expenses check box to include expenses in the report.
Currencies

This node contains all the currencies that Umbria supports. The following columns are shown:

  • Currency Code
  • Currency Name
  • Pivot (Is the currency an exchange rate pivot?)
  • Reportable (Is the currency reportable in Umbria reports?)
  • Status of the currency
Matter Statuses

This node displays basic information about matter/opportunity statuses. Built-in statuses include Closed, Converted to Matter, In Process, Inactive, Lost, Rejected, and Waiting for Matter.

Tip: The added Matter Statuses, will be available for selection in the Matter Profile Forms node, when adding Conditions and Sections.

Matter Sub-Statuses Here you can configure more granular statuses that can be used to track a matter's progress. It is possible to update a matter's sub-status from theForecastscreen.
Client Statuses This node contains a list of client statuses (e.g., Potential Client, Client, Terminated).
Sequences Values defined in this node are used to track the next auto-incremented number for entities such as opportunities, matters, and invoices.
Regions

This node stores region information and the import reference. You can also select a region to view or modify. The added regions will be available for selection when adding country information.

Countries

This node stores basic country information such as country abbreviations and whether the country is a favorite (meaning it will be selected often in Umbria and should be easily available). You can also select a country to view or modify the list of associated regions, if applicable. You can add State and State code to a country. Select the country and click the Add Button in the right panel.

Tip: The added Countries and the corresponding State will be available for selection in the Matter Profile Forms node, when adding Conditions and Sections.

Matter Display Name Template

In Umbria, the display of matter names can be customized based upon the firm’s preference. For example, you might wish for the matter number or the client name to precede the matter name, or vice versa. This node allows multiple matter name formats to be configured and for different formats to be assigned to specific matter types/subtypes, departments, or responsible lawyers.

After making changes here, you can use the Update Display Names function in the Matter Directory node to update existing matters accordingly.

Client Display Name Template

The display of client names (e.g., name followed by or preceded by number) can also be customized based upon the firm’s preference. This node allows multiple client name formats to be configured and optionally assigned to particular client roles, task code maps, or client statuses.

After making changes here, you can use the Update Display Names function in the Clients node to update existing clients accordingly.

Rate Card Display Name Template

The display of rate card names can also be customized based upon the firm’s preference. Here you can set up multiple rate card name displays that can vary by matter, by client, or by currency.

After making changes here, you can use the Update Display Names function in the Rate Cards node to update existing rate cards accordingly.

Vendor Display Name Template

The display of vendor names (e.g., name followed by or preceded by number) can also be customized based upon the firm’s preference. This node allows multiple vendor name formats to be configured and optionally assigned to Service Type and Sub-Type.

After making changes here, you can use the Update Display Names function in the Vendors node to update existing vendors accordingly.

Planning Phase Display Name Template

The display of the planning phase templates can also be customized based upon the firm’s preference. This node allows multiple planning phase display formats to be configured and optionally assigned to phases.

Analysis Settings

This node is used to manage SQL Analysis Settings (aka cube data).

Configuration and maintenance of the Analysis cubes are located in this module. See the Analytics section for setup and more configuration.

Applications

The settings in this node allow Umbria to interact with other applications such as the Umbria phone applications and the Excel Add-In. The applications available to you here vary based on what modules you have purchased for Umbria.

Matter Revenue Type The settings in this node allow you to add the revenue type for a matter, matter opportunity, client opportunity, or vendor opportunity. You can also include or exclude the revenue type from person realization, matter realization, or flag the revenue type as billable. Click the Add button to add a new matter revenue type.
Trigger Reasons

A few types of trigger reasons are available: 

  • Experience triggers are conditions that mark a matter or client as requiring action on the Experience Dashboard.
  • Fee Arrangementtriggers are used to launch tasks associated to fee arrangements (e.g., follow-up when an arrangement is about to expire).
  • Management(affects Partner Performance, Management tab and Practice Management Dashboard) triggers are used to alert partners when matters fall under a certain target (leverage, realization, profit margin) or reach a budget threshold.

The reasons configured here are used to set up the actual triggers in the Entity Triggersnode. Several trigger reasons are built in to the system.

Entity Trigger

In this node, you can use the reasons specified in the Trigger Reasons node to set up triggers that will automatically generate and assign tasks when certain conditions occur. When creating a new trigger, you can enter the following information:

  • Trigger Name: Internal identifier for the trigger.
  • Trigger Reason: Select from one of the reasons configured in the Trigger Reasonsnode.
  • Enabled: Select this checkbox if the trigger should be active in the system.
  • SQL query: Query used to identify entities or fee arrangements as requiring action.
  • Assign to user/Assign to group: Default assignee for the task generated by this trigger.
  • Due date in days: Number of days after generation the task must be completed.
  • Mode: Select Manual(tasks are generated only when you click theExecute triggers button in the Admin Panel) or Daily(tasks are generated as part of an automatic daily process). If you select Daily, you must specify a Time for the process to run each day. Once triggers are executed, you can view the execution status in the command log.
Entity Role In Umbria, people and entities are synonymous. Create, Edit or Remove Entity Roles. You can also map the entities/ employees to the roles. In the left column, click the Add button to add a new entity role. Enter the Role Name and the relevant Code to identify the role. Click Save. To map employees to an Entity Role, select the role in the left column and click on the Add button in the right column. In the Add Record window, select the Person, Department, Office, Join and Leave date from the drop down and click Save. The added employee / entity is now mapped to the Entity Role.
Entity Name Value You can view the entity names added and the number of times it is assigned. The right panel displays the Entity ID and the related Table name.

People Relationship Types

Inside the panel, users can configure the people relationship types to use for Secretarial Pairings and other pairings.

Out of the box Pairings:

These are for pairings between people only. The Is Pairing checkbox will be checked.

Out of the box People Relationship types not for pairing:

These types are for relationships that are not pairing types, and are typically used for client to person relationships.

To add a relationship type:

  1. Click add from the People Relationship Types panel.
  2. Name the type.
  3. Select the role of the primary person. This for example would be the secretary manager.
  4. Set a name for the relation. E.g. manager.
  5. Pick the related person security role. E.g. Secretary or Impersonator.
  6. Set a name for the related relation. E.g. secretary.
  7. Check is Pairing if this is for pairing use, and is a person to person relationship. For example, Biller, Evaluator, or Supervisory are examples of pairing.

 

Important note on Security roles set for Pairing Types:

Note: When configuring the primary or related security roles, do not attempt to set the role to a role like All Employees. Setting all employees to the related person role, will grant all employees access to impersonate anyone, and sees everything that person can see or do!

Users should use another existing role, like impersonator, secretary, manager; or create their own role limiting the access.