CRM 4.0 - Limited Access to Cases Only? RRS feed

  • Question




    We are a systems integrator that utilizes CRM to track all of our customer information, including the management of service activities and cases lreated to our clients.


    We are going to be implementing an answering service to enter cases, so we have created a security role for this user called Answering Service. This user has the following permissions:


    Core Records:


    Account - Read(Business Unit)/Append(User)/Append To(User)/Assign(User)

    Note - Create(Business Unit)/Read(Business Unit)/Write(Business Unit)/Append(Child BUs)/Append To(Child BUs)/Assign(Child BUs)/Share(Child BUs)

    Subject - Read(Org)/Write(Org)/Append(Org/Append To(Org)




    Case - Create(User)/Read(User)/Write(Org)/Append(Org)/Append To(Org)/Assign(Org)/Share(Org)


    Business Management


    Organization Setting - Read(Org)

    Business Unt - Read(BU)

    User - Read(BU)

    User Settings - Read(User)

    Team - Read(BU)

    Role - Read(BU)

    License - Read(Org)

    Currency - Read (Org)




    Form - Read(Org)

    View - Read(Org)


    Execute Workflow Job - Read(Org)


    I know it's fairly limited, and in doing this whenever we go to save the new case, we get thrown back with a permissions error, where 0x80048306 is the error code visible in the status bar.


    What additional settings at a minumum would I need to add in order to give members of the role permission to create a case?





    Tuesday, September 16, 2008 11:01 PM

All replies

  • Hi Chris,


    Some suggestions:


    • Give users at least user level read access to core entities like accounts, contacts, opportunities, orders, service calendar, etc, even if they are not going to be using those entities.  Also, make sure that they have append and append to rights for contacts.  If you are totally turning off access to core entities with security roles, you will find strange errors, as there are things going on behind the scenes that are not obvious that will cause errors.
    • Do not create a security role from scratch--copy one of the system roles and modify it.
    • If you want to hide certain entities that they won't need access to, use javascript to hide them on the form, or use the privilege element in the site map to hide them in the Wunderbar for certain users.  http://msdn.microsoft.com/en-us/library/cc150881.aspx
    • use the crm 4.0 diagnostic tool http://blogs.msdn.com/benlec/archive/2008/03/04/crmdiagtool4-for-microsoft-crm-4-0-has-been-released.aspx.  Enable platform trace on crm server, recreate the error, turn off platform trace, and look at the log file generated.  This would give you a more specific error message.


    Wednesday, September 17, 2008 3:06 AM