Restricting Access to Records
In this ArticleRestricting Records by the Login Record Restricting Records by Access Rights
Basic UnderstandingRestricting the user from accessing data is performed in two layers; ▪by the login record (Resource Group Restrictions tabpage) ▪by access rights.
So, a staff member having no restrictions set on their login record doesn't necessarily mean they have access to ALL project and staff records, they may be restricted by Access Rights (normal for smaller organisations). Alternatively, they may be restricted to only see projects appertaining to certain resource groups and be further restricted to only see those where they are the listed project manager (larger organisations). The following sections discuss each restriction layer in more detail.
Restricting Records by the Login Record
There are various options which can be used to restrict the user from accessing certain records.
Note: These restrictions can even be imposed for users with System Administration privileges. This allows the system to be configured so that you can have System Administrators for different resource groups.
Restrict Project Visibility by Staff Involvement (restricting by Service)
Restrict User To Resource Groups BelowHere you can specify if the user has no restriction, restrictions to Staff, Project, or Staff and Project records. Generally, if you are to impose Resource Group restrictions on staff members you would apply the restrictions to both Staff and Project records. However, the system does support great flexibility as you can also allow a staff member access to ALL projects but restrict them to only seeing staff in their resource group and visa-versa.
Resource Group AccessThis limits the user to seeing Staff and/or Projects records which appear in the 'Groups permitted access to;' list. You can therefore set up a staff member who works in the 'Europe' resource group to be able to see projects/staff records appertaining to the 'America' resource group but also restrict them from seeing records relating to the 'Asia' resource group.
Note: Task-less projects will still be visible unless they have the setting 'Restrict access to this project to the services listed below?' ticked. This is to ensure that staff who have resource group restrictions are not restricted from seeing overhead projects.
Project SelectionsNOTE: These settings function throughout both interfaces but can only be configured in the Windows interface. To add finer granularity you can configure the user record so that the user is only able to see very specific projects. Business cases for this could be to; •restrict the user to only see a specific clients projects •restrict a consultant to only have visibility of a particular project
Restricting Records by Access RightsYou can restrict access to records by restricting the user record to only have access rights to specific records in the Project and Staff listing grids. The terminology used is different between Project and Staff access rights as discussed below;-
Staff Related Access Rights
Project Related Permissions:
|
Any images shown may be representative of the previous version of
Timemaster
Report
a problem
Please report any errors on
this page to timemastersupport@equisys.com