Scenario

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“ Requires Timesheet Approval” Permission for Emily

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“ Requires Timesheet Approval” Permission for Emily
Alpha
Beta
Nova

Expected user actions per project:

Alpha Project	Beta Project	Nova Project

Alpha Project	Beta Project	Nova Project
Both users have full permissions, so the Alpha project can be submitted and approved by both users. Therefore, both users can see the Alpha project on the Timesheet Approvals page.	User 2 can only submit the Beta project; since they do not have approval rights, neither they nor other users can see the Beta project on the Timesheet Approvals page. User 1, however, has both permissions and can both submit and approve the Beta project.	User 1 has all the necessary permissions for the Nova project and can submit and approve it. User 2 does not have the “ Requires Timesheet Approval” permission, so they cannot submit the Nova project. Therefore, even if User 2 has worklogs for the relevant dates, it is expected that the Timesheet Approval Status panel on the “Your Work” page will display “Not Required” next to the Nova project. (FIG.1) However, since User 2 has the “Can Approve” permission, they can view and approve Nova projects submitted by other users on the Timesheet Approvals page. (FIG.2)

FIG.1

The statuses displayed on the Reports page are fully determined by the permissions assigned to each user.

In this scenario, for Diego, only the Beta project has been submitted. Therefore, his overall Timesheet status appears as Partial Submitted.(FIG.3) Since Diego has Can Approve rights for all projects, he sees Emily’s Timesheet status exactly the same as Emily does. (FIG.4 & FIG.5) By clicking the Timesheet Status button, he can access the detailed statuses of all projects. Additionally, if Diego is included in the report, he can submit or reject his own projects by clicking the same Timesheet Status button.

FIG.4 - Emily’s Timesheet status view on her own Your Work page

FIG.5

For Emily, in this scenario, the Alpha project has been submitted, the Beta project has been approved, and the Nova project cannot be submitted. As a result, Emily’s overall Timesheet status is shown as Partial Approved.

Since Emily cannot see the Beta project, and Diego’s other two projects are in the Open status, she sees Diego’s Timesheet status as Open rather than Partial Submitted on the Reports page. This is expected behavior because Emily’s report view is recalculated based only on the projects for which she has Can Approve permission. (FIG.6)

FIG.3

FIG.6

Scenario

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“ Requires Timesheet Approval” Permission for Emily

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“ Requires Timesheet Approval” Permission for Emily
Orion
Pulse
Atlas

Orion Project	Pulse Project	Atlas Project

Orion Project	Pulse Project	Atlas Project
Diego does not have the “Requires Timesheet Approval” permission. Therefore, even if he has worklogs for the relevant dates, it is expected that the Timesheet Approval Status panel on his Your Work page will display “Not Required” next to the Orion project, and he should not be able to submit the project. However, since he has the “Can Approve” permission, he is expected to be able to approve or reject Orion projects submitted by other users on the Timesheet Approvals page. Emily has the “Requires Timesheet Approval” permission for Orion. Therefore, she can perform actions such as submit or revoke on this project. However, because she does not have the “Can Approve” permission, she cannot see Orion projects submitted by other users on the Timesheet Approvals page. [They can see the project only when they filter by -> user to select themselves.(FIG.7)] In other words, no information about Orion projects is visible to Emily on this page, and she cannot perform any approve/reject actions on them.	Neither Diego nor Emily has the “Requires Timesheet Approval” permission. Therefore, even if they have worklogs for the relevant dates, it is expected that the Timesheet Approval Status panel on their Your Work pages will display “Not Required” next to the Pulse project, and they should not be able to submit the project.	Both Diego and Emily have the “Requires Timesheet Approval” permission. Therefore, they are expected to be able to perform actions such as submit or revoke on this project. However, since they do not have the “Can Approve” permission, they cannot see Atlas projects submitted by other users on the Timesheet Approvals page. [They can see the project only when they filter by -> user to select themselves.(FIG.7)] In other words, no information about Atlas projects is visible to Diego or Emily on this page, and they cannot perform any approve/reject actions on them.

Users cannot see projects for which they do not have Can Approve permission on the Timesheet page.

In this scenario, Diego’s overall Timesheet status and project-based statuses are shown in the screenshot below (FIG.9). Since he does not have permissions for the Orion and Pulse projects, he cannot take any actions on them. However, by submitting a single project (Atlas) and having it approved, his overall Timesheet status is displayed as Approved. For Emily, even though the Pulse project is “Not Required“, her overall Timesheet status is shown as Rejected because the Orion project has been rejected.(FIG.10) (In other words, if even one of the submitted projects is rejected, the overall Timesheet status is automatically set to Rejected. This is the expected behavior.)

Additionally, if Diego wants to view Emily’s Timesheet:
Since Diego does not have access to the Atlas project, but does have Can Approve rights for the other two projects, Diego sees the same overall Timesheet status as Emily.

The Status button is enabled as long as Diego or the user whose Timesheet is being viewed (in this case, Emily) has the Requires Timesheet Approval permission for at least one project, or Diego has Can Approve rights for at least one project in that Timesheet. In such cases, Diego can also view the project-based statuses.

On the other hand, if Emily wants to view Diego’s Timesheet:
Emily only has Can Approve rights for the Pulse project. However, since Diego cannot submit this project, and Emily has no access to any of his other projects, she cannot access any of Diego’s projects. Therefore, the Status button is disabled, and the overall Timesheet status is shown as Open instead of Approved. In summary, showing Open here is not a bug but the expected behavior, due to Emily’s permissions.

FIG.9

FIG.10

The Status button is disabled if Emily has the Requires Timesheet Approval permission for at least one project but Diego lacks permissions for those projects, or if Diego has Can Approve rights for at least one project in his Timesheet but Emily lacks permissions for those projects. In these cases, project-based statuses are not displayed.

Scenario

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“Requires Timesheet Approval” Permission for Emily

Project	“Can Approve” Permission for Diego	“ Requires Timesheet Approval” Permission for Diego	“Can Approve” Permission for Emily	“Requires Timesheet Approval” Permission for Emily
Vertex
Core
Horizon

Vertex Project	Core Project	Horizon Project

Vertex Project	Core Project	Horizon Project
Diego does not have the permission, so he is not expected to submit the project. However, since he has the Can Approve permission, he can see other users who submitted the Vertex project on the Timesheet Approvals page and perform approve/reject actions. Emily has neither Requires Timesheet Approval nor Can Approve permissions. Therefore, she cannot submit the project in any way, cannot see other users who submitted the Vertex project on the Timesheet Approvals page, and cannot perform approve/reject actions.	Diego has the Requires Timesheet Approval permission, so he is expected to be able to submit the project. However, since he does not have the Can Approve permission, he cannot see other users who submitted the Core project on the Timesheet Approvals page, nor can he perform approve/reject actions. Emily has neither Requires Timesheet Approval nor Can Approve permissions, so she cannot submit the project and cannot see or take action on other users’ submissions.	Neither Diego nor Emily has Requires Timesheet Approval or Can Approve permissions. Therefore, neither of them can submit the project, see other users who submitted it on the Timesheet Approvals page, or perform approve/reject actions.

For Emily and Diego, no records will appear under any filters because she has neither Can Approve permission nor any project she can submit. (FIG.11)

FIG.11

When Diego views Emily’s Timesheet, since the Status button is disabled and Diego has no permissions for the relevant projects, and Emily cannot submit them, the status automatically appears as Open and is disabled.

Since Emily has no permissions for any project, the Timesheet Approval Status button is expected to be disabled.

If Emily views Diego’s Timesheet, since she has not performed any actions on her own Timesheet, her status is shown as Open. Even if Diego’s overall Timesheet status is Submitted, Emily sees the status as disabled and Open in the Reports page because she has no permissions for any project.

How It Works in Practice

Scenario

Expected user actions per project:

Scenario

Scenario