“Sensitive projects” - block working time comments by contract
Birgit Pfisterer
With an authorization role that has access to projects but no personnel rights, it is possible to access projects at all times, including sensitive working hours, e.g. the GF, including reading comments.
A variant is required that grants access to project and contract processing and yet has no access to sensitive time entries. Would it be possible to hide the Times tab as soon as a project contains sensitive working hours and the accessing person has no extended personnel rights?
Alternatively, could “sensitive projects” be set up that are only visible to people with the “All Permissions” role?
Birgit Pfisterer
If you have access to a project, you automatically have access to the “Times” tab, even if only in the form of reading rights. So when GF books times and posts comments that may be worth protecting, these are visible, even if “sensitive working hours” is checked for the role of GF (All Permissions). I'm afraid that's something we haven't thought through to the end. When are working hours actually protected or where/how are they protected? I would assume that if working hours are protected, they are not visible anywhere, unless someone has extended personnel rights.
Arne Semmler
Is this really a “bug”, i.e. that working hours of the owner, for example, should be protected, are visible despite activated settings? We also have the setting not per project, but per authorization role:
S
Simon Winkler
Arne Semmler Hi Arne,
Logically speaking, as Birgit explained to us, the check mark you marked in the screenshot should mean that the people who then check “Sensitive working hours” in the authorization role should not see time entries in any area (except for people with extended personal rights), neither in projects nor elsewhere.
At least when checked for “Working hours, e.g. owner protected” and “Sensitive working hours”, we do not see any effect anywhere that anything has been concealed or protected. How exactly is it to be understood then?
(We would have to do this in order to be able to understand whether it is really a bug, or whether the function is just misunderstood and we didn't understand something - then it would be more of a feature request that you can hide or hide internal projects such as an overhead project for HR, etc., from people who should have access to all projects.
Arne Semmler
Simon Winkler Hi Simon, I'm leaving this on the bug list, because it's supposed to work the same way: The comments on time entries from people who have this setting should not be visible in the time journals. We check whether it is a bug or whether an additional setting was forgotten to set.
S
Simon Winkler
Arne Semmler Hi Arne,
Apparently (or seen by me for the first time), the tooltip for “Sensitive working hours” has now been adjusted so that it corresponds to the current status quo, see screenshot.
However, I would still find it very helpful if the option could either apply globally to all time entries or leave it that way and introduce “sensitive projects” instead.
We have now tried to adjust all time entries for our sensitive internal projects (e.g. personnel), but this is a Sisyphean task with a comment history dating back to the turn of the millennium. Since we sometimes have quite detailed real names of MA etc. in the comment columns, we unfortunately cannot yet use Projo for the purpose as we would like to do.
If I take the tooltip seriously now, it should only be possible for project managers and managers to see the times in the project. If someone now has the “all projects” permission, Projo automatically sees them as a “project manager” and can therefore also see the time entries of sensitive entries in the other projects.
Maybe another case for the wish list or for one more check :-)
Arne Semmler
Simon Winkler Before introducing such a function, you would have the option of dividing up the relevant internal projects or creating new ones for them. If you do not assign certain projects to all employees, but only to those who should/are allowed to view the comments, the old ones would in any case be protected and new ones can be differentiated. For the same reason, we also work with several internal projects for different purposes here at projo. I also know it from many of our clients' offices. If there are any questions about this, we would be happy to clarify this via the support channel.
S
Simon Winkler
Arne - thanks for the really quick answer - yes, we have now solved that and created an extra “Acquisition” project role for our acquisition employee, with which we now assign her to all ongoing projects. However, since she has to access old projects again and again (for acquisition, but also PR purposes), the check mark “All projects (except “sensitive projects”) described above would be more practical, as we currently have in Projo incl. Old projects talk about 517 projects, which of course are not all relevant to the topics, but certainly mean work to adjust the project role. We already use various internal projects for time entry :-)