Section 12.6 Security Policy

Section 12.6 Security Policy


Section 12.6  Creating a Security Policy

Administrators can create a security policy for a user or a role. Components of a Policy include the level (user/role), accessibility settings (group/user/role), and action settings. Each Security Policy must address all areas of WIB Review: who can access each area, what actions are allowed and to whom or which role/user the policy applies.

Section 12.6.1                  Policy Name

Name the policy in such a way that it describes either the role or an individual user’s job function. It is suggested the Policy Name is Different than the Role or Username as staff and responsibilities change over time and you want the Policy to reflect the functionality of the policy which will persist over time. You can change the name of the policy.

Section 12.6.2                 Assign the Policy

You must assign the Policy to a specific user or a role. If you access the Policy from a Role or User, the Policy Summary will populate with the User or Role the Policy is assigned to.

Section 12.6.3                 Security Policy Stepper (Roadmap)

The Security Policy Stepper guides the administrator through the process of defining a Security Policy.

Section 12.6.4                 Security Policy Definition (SPD) (Roadmap)

The Security Policy must define which actions roles and/or users are allowed to perform for all the features.

Section 12.6.4.1           Dashboard SPD

Section 12.6.4.1.1                Dashboard Page Accessibility

You can restrict access to the Dashboard. If you do not want the user or a set of users, referred to as “users”, with a particular role to access the Dashboard in its entirety, then turn off Page Access. If they have access, you must define what actions they (the users) are allowed to perform.

Section 12.6.4.1.2               Dashboard Page Actions

Each Page in WIB Review has actions that can be performed that are specific to the page or a section of the page.

Section 12.6.4.1.2.1    View

Users are only allowed to view the dashboard. They cannot customize the dashboard.

Section 12.6.4.1.2.2    Design

Allows the user to customize the dashboard. Report Tiles can be added to the dashboard, resized, and organized to the user’s preference. Refer to Reports to create and save a report. Users can add private or public reports to the dashboard.

Section 12.6.4.1.2.3    Print

Users can print a dashboard to a PDF for sharing.

Section 13.6.4.1.2.4   Export

Users can export a dashboard to a PDF or to an excel spreadsheet. The report metadata and the chart can be exported. The chart is exported as a picture and will no longer dynamically update if any metadata supporting the report is changed.



    • Related Articles

    • Section 12.1 Password Policy

      Section 12.1 Password PolicyA password policy is a set of rules designed to enhance computer security by encouraging users to employ strong passwords and use them properly. The computer system will force users to follow the password policy. WIB™ ...

    • Section 12 Security Management

      Security Management Security Management allows Administrators to set up users, groups, and roles which combined become a Security Policy. Policies are vital when it comes to keeping proper access rights to your most sensitive data. The ability to ...

    • Section 12.4 Roles

      Section 12.4 Roles A security role is a collection of privileges in a workspace. Users can be assigned to a role and inherit the permissions defined in the role. Roles can be added to groups and will be restricted to performing the actions defined by ...

    • Section 12.3 Groups

      Section 12.3 Groups A group of users are given access to work areas (projects/collections) that all need access to the same resources. Groups can be created based on individual users that all need access to certain resources, they can be created ...

    • Section 12.5 Users

      Section 12.5 Users A user is associated with an access license (UAL). They are not shared by Users; each User must have their own UAL. Once a User has their own UAL, it does not matter how many machines they log in from. Users are assigned a Role and ...