Can't relate with forbidden user record. READ access required

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rfrancocantero
    Member
    • May 2020
    • 69

    Can't relate with forbidden user record. READ access required

    Hi,

    Since the last upgrade when a user wants to create an opportunity it throws this error "Error 403: Access denied Can't relate with forbidden user record. READ access required". I've tried to revise all role permissions but they seem okay. Could this be another issue that I;m overlooking?

    See attachment.
    Attached Files
  • victor
    Active Community Member
    • Aug 2022
    • 727

    #2
    Most likely, this User does not have sufficient rights to view this Account:

    Click image for larger version  Name:	image.png Views:	0 Size:	56.7 KB ID:	102108
    Give to him that permission and your error should disappear.​

    Comment

    • yuri
      Member
      • Mar 2014
      • 8440

      #3
      Hi,

      How exactly the user creates the opportunity?
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

      Comment

      • rfrancocantero
        Member
        • May 2020
        • 69

        #4
        Actually, the user does have rights to this account. The account is assigned to this user. It doesn't matter how the opportunity is created; either through Accounts --> Create Opportunity or through Opportunities directly and then linking it to the Account. What type of rights should be needed for this?

        It appears to be with all users and I remember upgrading last week to the most recent version of Espocrm. Could this be the culprit?
        Last edited by rfrancocantero; 01-30-2024, 10:11 AM.

        Comment


        • victor
          victor commented
          Editing a comment
          Please send a screenshot of this user's Role settings. I am interested in his rights for Opportunity and Account.
      • rfrancocantero
        Member
        • May 2020
        • 69

        #5
        Sure!

        Comment

        • shalmaxb
          Senior Member
          • Mar 2015
          • 1602

          #6
          I guess, the user has to be in a team with this role and from your first screenshot in the first thread, there is no team.

          Comment

          • rfrancocantero
            Member
            • May 2020
            • 69

            #7
            Hi, I think I solved it but I don't understand it though. When I give the role the following permission, they were able again to create it.

            Comment

            • tayling
              Member
              • Apr 2023
              • 45

              #8
              Hi rfrancocantero - well done I had the same issue and it fixed for me too. I gave access to email template to the users team which I thought usually works but they got the error 403 message. I did what you suggested and works fine.
              Thanks

              Comment

              Working...