web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Restrict User Access to Project Details

(0) ShareShare
ReportReport
Posted on by 195

Hi All,

I found that the OOTB project security roles are not great for applying to a user who only needs access to add time to projects.

The Project Resource role gives way too much access to a user and there is noting below that.

I created my own role based on the Project Resource one and I have reduced it down to a level where the user can enter time but has no access to anything else, for the most part!

However, my issue arises when a user creates a new time entry or edits a time entry row. In the quick create forms the project and task are listed and by clicking these fields the user gets read only access to the project, added to that the can click on user names and roles and go much further with just the read only access.

I have tried field level security but as you know I can't hide every field and that would just get out of hand after a while trying to manage.

Is there something else I am missing or could I put in some JavaScript On Load for the two time entry forms to block users clicking the project fields?

Regards,

Jason

I have the same question (0)
  • MohitGarg Profile Picture
    50 on at

    Hi Jason,

    You can try creating a new Form with minimal info and leverage security roles to show the revised form to the users who are only using Time sheet feature. 

    Best, 

    Mohit

  • Suggested answer
    Lucky Dog Profile Picture
    670 on at

    Hi. I suggest you give these users only access to the 'Project Resource Hub' app and also remove Expenses from the sitemap. They will be able to select Projects and Tasks that they are scheduled to but will have no access to Project records, tasks, users etc.  Alternatively you can create a different security role that only has append-to privileges to these entities and so won't enable them to view records, just append them.  The first option is much more straightforward and should work with minimal config.

  • JasonTwi Profile Picture
    195 on at

    Hi All,

    So I refined my custom security role a bit more by just going through it line by line.

    Also, I did implement the field level security on the fields in question, it's okay for now.

    MS couldn't provide anything outside of the JavaScript suggestion.

    Lastly, I followed Lucky Dog's suggestion of removing some elements of the Project Resource App.

    Again not ideal but it did help lock down some of the access.

    Regards,

    Jason

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 522 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans