Contents x
    Permission Details
    • 8 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Permission Details

    • 8 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Permissions in Agility Blue work on a level-based hierarchy. There are five levels starting from no rights to full rights where each right starting with “View” gains all of the rights of the previous rights: None, View, Create, Edit, and Delete. If a permission is set to the “None” right, than Users of that Permissions Group will not have permission to see or interact with the resource the permission is protecting.

    Each permission will have a set of at least two or more icons to the right of each permission. The icons represent the rights available and the rights set for a permission based on the color of the icon. An icon is lit blue if the right is set for the permission and gray if it is not set. A red icon is reserved for the None right.

    Permission Rights

    None

    Users in this Permissions Group will not have permission to see or interact with the resource the permission is protecting.

    View

    Users in this Permissions Group will have permission to see or interact with the resource the permissions is protecting. They will not be able to create, edit, or delete.

    Create

    Users in this Permissions Group will have permission to see, interact , and create the resource the permission is protecting. They will not be able to edit or delete.

    Edit

    Users in this Permissions Group will have permission to see, interact , create, and edit the resource the permission is protecting. They will not be able to delete.

    Delete

    Users in this Permissions Group have full rights to see, interact , create, edit, and delete the resource the permission is protecting.

    There are many permissions where all rights may not apply. In these cases, the icon will not be visible. For example, the Attachments permission in the Matters category does not allow for editing attachments because the system does not allow for editing Attachments – attachments can only be uploaded or downloaded. Therefore, only the None, View, Create, and Delete rights are available to select.

    Dependencies

    Permissions may also have dependencies. If a permission is dependent on another permission rights, the description of the permission will mention this. For example, the Notifications permission for the Settings category mentions that at least view rights on the “Settings” permission is required. If the dependent permission requirement is not first set, a triangle warning icon will show up next to the permission that the user is trying to change. In order to change that permission rights, the user will need to allow the dependent permission the required rights first.

    If a permission that has dependent permissions is changed where the dependent permission requirement is no longer met, the dependent permission rights will be changed to None.

    Clients

    The Clients permissions category allows administrators to set rights for users that pertain specifically to the Clients list view, the Client details page, and the focus tabs found on the Client details page. This category has five available permissions: Client, Clients Associated with Other Users, Insights, Matters, and Attachments. All permissions in this category are dependent on at least the Client permission to have view rights. The Matters permission also requires that the Matter permission have view rights under the Matters category.

    Clients Associated with Other Users: What does it mean?

    This permission allows users to see Clients where the User has some kind of association throughout the Client hierarchy. The Client hierarchy is a Client with any of its Matters, any of its Matters’ Projects, and any of its Matters’ Projects’ Tasks. An association is any of the aforementioned Objects where the User is either a Creator, an Owner, or an Assignee. Therefore, with this permission set to none, users with assigned Tasks would only be able to see the Clients those Tasks belongs to.

    If you would like users to see all Clients regardless of association, set rights on this permission to “View”.

    In order to view the Matters focus tab on the Project Details page, you will also need to have at least View rights for the Matter permission in the Matters category.

    Contacts

    The Contacts permissions category allows administrators to set rights for Users that pertain specifically to the Contacts list view, the Contacts details page, and the focus tabs found on the the Contact details page. This category has two available permissions: Contact and Projects. The permissions in this category are dependent on at least the Contact permission to have view rights. The Projects permission requires that the Project permission have view rights under the Projects category.

    Dashboard

    The Dashboard permissions category allows administrators to set rights for Users that pertain specifically to the available Dashboard views. Dashboard views show Projects and Tasks that are not yet finished.

    Matters

    The Matters permissions category allows administrators to set rights for Matters that pertain specifically to the Matters list view, the Matters details page, and the focus tabs found on the the Matters details page. Matters are the first link in the Client hierarchy and contain Projects.

    Matters Associated with Other Users: What does it mean?

    This permission allows users to see Matters where the User has some kind of association throughout the Matter hierarchy. The Matter hierarchy is a Matter with any of its Projects and any of its Projects’ Tasks. An association is any of the aforementioned Objects where the User is either a Creator, an Owner, or an Assignee. Therfore, with this permission set to none, users with assigned Tasks would only be able to see the Matters those Tasks belongs to.

    If you would like users to see all Matters regardless of association, set rights on this permission to “View”.

    In order to view the Projects focus tab on the Matter details page, you will also need to have at least View rights for the Project permission in the Projects category. In order to allow users to click on the Client Link, you will need to have at least View rights for the Client permission in the Clients category.

    Misc

    All Misc Objects are located within the Vertical Ellipsis menu item on the Navigation Bar. These permissions allow administrators to set the rights of the lists and the ability to edit, create, or delete the respective Objects on their list pages. These lists consist of the Tag, Media Type, Form, Object, Billing Type, and Report Objects.

    Setting the rights of these Permissions to None only sets their “List” visibility. Setting the Form permission to “None”, for example, does not prevent a user from selecting a Form when creating a new Task (provided the User has those permissions). It only prevents them from seeing the list of Forms on the vertical ellipsis menu or creating/deleting forms.
    Setting the rights of Tag, Media Type, and Form Objects to “View” or lower will also prevent the User from seeing the Quick Create links located on various dialogs (such as creating a new Form on the New/Edit Tasks dialog).

    Projects

    The Projects permissions category allows administrators to set rights for Projects that pertain specifically to the Projects list view, the Projects details page, and the focus tabs found on the the Project details page. Projects are the second link in the Client hierarchy and contain Tasks.

    Projects Associated with Other Users: What does it mean?

    This permission allows users to see Projects where the User has some kind of association throughout the Project hierarchy. The Project hierarchy is a Project with any of its Tasks. An association is any of the aforementioned Objects where the User is either a Creator, an Owner, or an Assignee. Therfore, with this permission set to none, users with assigned Tasks would only be able to see the Matters those Tasks belongs to.

    If you would like users to see all Projects regardless of association, set rights on this permission to “View”.

    In order to view the Tasks focus tab on the Project details page, you will also need to have at least View rights for the Task permission in the Tasks category.

    Project Details Action Pane

    The Project details Action Pane is a pane located on the far right of each Project details page. The pane consists of actionable fields related to a Project consisting of the Cancel Project Button, Received Date, Due Date, Invoiced Date, Requester, Requester Notification Icon, Owner, Priority, Pricing, Notifications, and Approved fields. Administrators may set the permissions for any of these fields to control the visibility or editability of each field.

    Tasks

    The Tasks permissions category allows administrators to set rights for Tasks that pertain specifically to the Tasks list view and Tasks located on the Projects details page. Tasks are the third link in the Client hierarchy.

    In order to view the Tasks focus tab on the Project details page, you will also need to have at least View rights for the Project permission in the Projects category.
    If the permission for Task is set to None, the Tasks drop down quick view on the Project grid will no longer be available. Also note that the Task focus tab on the Project details page will display a “Not enough Permissions” notice. Thus, it is generally a best practice that if a User is allowed to view Projects, than they should also be able to view Tasks.

    Users

    Users
    The Users permissions category allows administrators to set rights for the visibility of User Names in a Workspace.

    Other User Names: What does it mean?

    Allows users to see other user names throughout the Workspace. Users will see "Agility Blue User" If this permission is set to "None" for users other than themself. Note that user-based pick lists (such as the "Owner" or "Assign To" drop down lists) are not affected by this permission. Thus, if the user has, for example, view rights for the "Assign Tasks to Others" permission, the user will still be able to see the other user names in that list if the rights for this permission is set to "None."

    If you would like users to see any User’s names, set rights on this permission to “View”.

    What's Next