Security Group File Explanation

Security is robust and detailed, providing control down to a very granular level. Because of this, the security group files can become very long. An explanation of the various sections of the security group file is provided below. An explanation of button security is also provided.

High Level Folders

Collapse and expand the nodes on the security group file navigation tree as needed. The image below shows the high level nodes, with all the sub nodes collapsed. The main sections of the file are easier to identify if the sub nodes are collapsed.

Nodes in Security Group File

• SELECTALL: Click this check box to select every node in the navigation tree. This will give the security group access to everything.

• Primary Companies: This is the node that holds all company information. In the image above there are two primary companies: Holding Company and International Holding Company. Click the check box next to the Primary Company name to grant access to every subsidary company, page, plan, transaction and button. If this check box is unchecked, then access can be granted manually on a more detailed level.

• Holding Company: This is the name of one of the primary companies. Check this box to grant access to everything relating to that company. Every company has nodes for pages, plans and subsidiary companies. This will all be selected if the box is checked at this level.

• Primary Company Pages: Expand this node to see all of the pages relating to the primary company. Each page will be listed separately. Expand each page to see the buttons available on the page. Grant access to the entire page, or grant access to specific buttons on that page.

• Primary Company Plans: Expand this node to see all of the plans associated with the company. Click the check box next to the plan name to grant access to everything in that plan, or expand the sub nodes to be more specific. Each plan contains the following:

• PlanPages: Expand this node to see all pages associated with the plan. Grant access to the entire page, or to specific buttons on the page.

• PlanTransactions: Expand this node to see all transactions associated with the plan. Grant access to the everything related to the transaction or to specific buttons related to the transaction.

• Subsidiary Companies: This is the node that holds all subsidiary company information. The hierarchy is the same as the one for Primary Company. Each company has Subcompany Pages and Subsidiary Company Plans.

• SubCompany Pages: Expand this node to see all of the pages relating to the subsidiary company. Each page will be listed separately. Expand each page to see the buttons available on the page. Grant access to the entire page, or grant access to specific buttons on that page.

• Subsidiary Company Plans: Expand this node to see all of the plans associated with the subsidiary company. Click the check box next to the plan name to grant access to everything in that plan, or expand the sub nodes to be more specific. Each plan contains the following:

• PlanPages: Expand this node to see all pages associated with the plan. Grant access to the entire page, or to specific buttons on the page.

• PlanTransactions: Expand this node to see all transactions associated with the plan. Grant access to the everything related to the transaction or to specific buttons related to the transaction.

Any of the main nodes described above can be expanded to reveal the related sub-nodes. Collapse sections that aren't needed in order to make navigation easier.

Button Security

The buttons in OIPA have a layer of security around them to restrict access. Button security is set at the Company, Plan and Transaction level. An explanation of each level of button security is provided below.

Company Level Button Security

Windows and Screens in OIPA have buttons that initiate actions. At the PrimaryCompanyPage level, most of these windows and screens can be accessed from the Main menu or Secondary menu in OIPA. For example, Client shown in the image below refers to the Client link on the Main Menu in OIPA. When a client record is selected from this link and is open in OIPA, the Secondary Menu across the top of the screen can have two buttons: AddActivity and Inquiry. There is also a Save button at the bottom of the client record. The security for these buttons is listed in the Security Group file as shown below. If the buttons are checked in the Security Group file, then the buttons will appear in OIPA. If they are not checked, they will not appear in OIPA.

Note: The AddActivity button will not appear unless the client record is associated with a policy, even if security is checked in the Security Group file. Without a policy, there is no way to process activities. The Inquiry button will only appear if an Inquiry has been configured at the Client level.

Each Primary Company Page has a sub node for button security. Open each page to see the available buttons. Check or uncheck the buttons as needed.

Note: Company level activities are not supported in this release. The ActivityDetail page contains options for this level of button security, but it is not supported at this time.

Security for Client Screen Buttons in OIPA

Plan Level Button Security

A deeper dive into the application reveals buttons at the plan level. The buttons selected at this level will only apply to a specific plan. Each plan has pages that correspond to the windows and screens in OIPA, with security for the buttons included on those windows and screens. For example, on the Guaranteed Level Premium Term plan, the Activity screen has four buttons: AddActivity, AutoProcess, Inquiry and ProcessAll. Granting access through the Security Group file means that anyone from the Security Group can log into OIPA and access those buttons when working with policies on the Guaranteed Level Premium Term plan. The images below show where the buttons appear in OIPA.

Activity Screen Buttons in Security Group File

Activity Screen Buttons in OIPA

Transaction Level Button Security

The most detailed level of security happens at the transaction level. Each transaction associated with a plan will have its own set of security around the buttons and icons that affect that transaction. Users will only be able to access the buttons related to a particular transaction if access is granted in the security group file. An explanation of the buttons and icons available for transaction security is listed below.

• ActivityDelete: This is the delete icon that appears to the right of the activity on the Activity screen.

• ActivityDetail: This is the Activity Detail icon that appears to the left of the activity on the Activity screen.

• ActivityError: This is the error icon that appears to the right of the activity on the Activity screen.

• ActivityProcess: This is the process icon that appears to the right of the activity on the Activity screen.

• ActivityProcessNUVPending: This is the warning icon that appears when NUVs are still pending for an activity.

• ActivityRecycle: This is the recycle icon that appears to the right of the activity on the Activity screen.

• ActivityRequirement: This is the requirement icon that appears to the right of the activity if a requirement is attached to the activity.

• ActivityResult:

• ActivityReverse:

• Ok: This is the OK button inside the Activity Detail window.

• RequirementDelete: This is the right-click option inside the Requirement window. This window opens when the requirement icon is clicked.

• RequirementDetail: This is the right-click option available when a requirement is clicked inside the Requirement screen.

• RequirementOK: This is the OK inside the Requirement screen. This screen opens when the requirement icon is clicked.

Security for Transaction Buttons in OIPA