locked
CRM Create Address Permissions RRS feed

  • Question

  • I think I have a problem. We have a requirement to allow users to create/edit addresses for contacts, but not be able to create/add accounts.

    We are on-premise, rollup 12.

    It appears the "new address" permission is tied directly to the "Account" permission so if they can add or edit addresses they can can also add/edit accounts. This resulted in me being unable to create or edit addresses through the "more addresses" entity.

    I tested this by making a copy of the System Administrator security role, assigning it to my test user, and then unchecking the "Create" button on the account entity.

    This seems like strange behavior to me, and I know the address entity is a fickle beast and functions differently than "normal" entities.

    Is there a way around this short of allowing everyone to create organizations and then controlling it with a plugins that check if the person has a certain security role to prevent them from adding or modifying organizations?



    • Edited by MProper Friday, November 22, 2013 4:05 PM more detail
    Friday, November 22, 2013 3:38 PM

All replies

  • It seems really strange but you could write JavaScript on Onload event of account form to check user security role and if user don't have role you could show alert and close the form.

    http://mscrmbi.blogspot.com/2012/02/get-user-security-roles-in-jscript.html

    Or you could also create custom entity lets say CreateAccount and assign create permission for those users can create account and read user permissions/privileges. Please refer following link

     http://vikramxrm.blogspot.com/2013/10/read-user-privileges-using.html

    Hope this helps. If you get answer of your question, please mark the response as an answer and vote as helpful !
    Vikram !

    Friday, November 22, 2013 5:00 PM
  • Thank you for the respoonse.

    We might have to use the javascript thing, but make it pretty configurable. The issue we have is we have multiple deployments, and then BU's (departments) within those deployments, and then it's up to the customer if they want to allow their staff (or just team leads) to add/modify accounts.

    So deployment 1 might let staff, deployment 2 only lets leads and deployment 3 has one department(BU) who lets staff while the other departmentment only lets team leads.

    Grrrr......I'm hating this permission thing already. Why are address permissions tied to accounts?  **shakes fist**  Actually I know why based on my knowledge of how addresses work in CRM, but it's now causing me headaches since apparently I can't let them add/edit addresses for contacts while not letting them add/edit accounts.

    Maybe we can figure out something.

    PS - I wonder if MS purposely makes this forum not work in Chrome (the submit button doesn't work) :(


    • Edited by MProper Saturday, November 23, 2013 4:26 PM edits
    Saturday, November 23, 2013 4:25 PM