Expandir minha barra de realizações na Comunidade.

Submissions are now open for the 2026 Adobe Experience Maker Awards.
SOLUCIONADO

Restrictions on where users can log time

Avatar

Level 2

In the WF instance I manage, users are allowed to log time directly on projects. However there is one project where we only want time logged to tasks. Any ideas for limiting the objects users can log time to (in this case: tasks on a specified project), when the instance is configured to allow time logged directly to projects? 

1 Solução aceita

Avatar

Resposta correta de
Community Advisor

One possibility is the project sharing or access setting. I'll show it in the sharing dropdown (screenshot) but you can also find this in the access section when you edit the project.

 

In this screenshot I show how I have shared a project with a team using "contribute" access, and then clicked on the additional options to click off the ability to Log hours.

 

This sharing is sent down to all project tasks (inherited permissions) so you MIGHT need to re-share the tasks and make sure the "log hours" is checked on (either way, I expect you to test your system thoroughly). So basically this two step process will remove the ability to log hours on a project and give that ability to the tasks. Depending on what you discover in your experiment, it may end up being a bit onerous, but maybe you can control the sharing using templates, and share it very broadly.

 

Screenshot 2025-05-13 155505.png

Ver solução na publicação original

5 Respostas

Avatar

Level 2

I should have mentioned: we have Fusion. So maybe a Fusion scenario that automatically deletes time logged on the project and tags the user to a comment asking them to re-log the time to a task. 

Avatar

Community Advisor

 

Hi @JulieCh11,

 

If you go the Fusion route, rather than delete the hours, perhaps moving them (eg to a "Misplaced Hours" Task) would be more effective since it:

 

  • preserves the hours
  • preserves any hour comments
  • automatically audits the behavior
  • makes such hours easily reported (and "deliverable) as exceptions
  • allows end users to then (more easily/less putatively) move them to the correct Task

 

I am interested in hearing which approach you decide to use. Good luck!

 

Regards,

Doug

 

cc: note to self @Doug_Den_Hoed__AtAppStore 

 

Avatar

Level 2

thanks this is also a potential solution! My only concern about moving the hours (as opposed to deleting) is it puts the onus on the user to correct their mistake, which I suspect they'll put-off doing until someone tells them to. It would also allow them to submit their weekly timesheet with hours entered into the wrong object  

Avatar

Resposta correta de
Community Advisor

One possibility is the project sharing or access setting. I'll show it in the sharing dropdown (screenshot) but you can also find this in the access section when you edit the project.

 

In this screenshot I show how I have shared a project with a team using "contribute" access, and then clicked on the additional options to click off the ability to Log hours.

 

This sharing is sent down to all project tasks (inherited permissions) so you MIGHT need to re-share the tasks and make sure the "log hours" is checked on (either way, I expect you to test your system thoroughly). So basically this two step process will remove the ability to log hours on a project and give that ability to the tasks. Depending on what you discover in your experiment, it may end up being a bit onerous, but maybe you can control the sharing using templates, and share it very broadly.

 

Screenshot 2025-05-13 155505.png

Avatar

Level 2

thank you this worked!