locked
CRM 4.0 Allowing Import Permissions Security Role RRS feed

  • Question

  •  

    Hi everyone.

     

    I have the systems administrator user type set up for the main sys admin to give them the ability to administer anything within CRM. They also have the ability to load in data and use the bulk import wizard.

     

    As part of our main user security role, we wish to give them the ability to also import data into CRM. We have a custom security type created and have issued it permissions.

     

    When logged in to a user with the new security role, the import wizard displays an error and no jobs can be seen. After attempting to give the role a number of new privilages I set the privilages to match the sys admin role, (all on) and the user still could not import data onto CRM.

     

    What could be causing this?

     

    Thanks

    Monday, December 1, 2008 11:56 AM

Answers

  • did you create a new role totally from scratch?  If so, you will see problems like this--even though everything looks to be ok, there are some behind the scenes permissions that do not get set.

     

    What you want to do is copy one of the system roles--select a role such as sales manager, hit actions/copy role--this will create a new role that is an exact copy of the system role, then scale back the permissions as desired.  And make sure that they have at least user levelread access to all core entities (account, opportunities, orders, invoices, service calendar, etc), even if they don't use them.  If not, you will get errors due to dependancies that aren't obvious.

    Monday, December 1, 2008 12:10 PM
    Moderator

All replies

  • did you create a new role totally from scratch?  If so, you will see problems like this--even though everything looks to be ok, there are some behind the scenes permissions that do not get set.

     

    What you want to do is copy one of the system roles--select a role such as sales manager, hit actions/copy role--this will create a new role that is an exact copy of the system role, then scale back the permissions as desired.  And make sure that they have at least user levelread access to all core entities (account, opportunities, orders, invoices, service calendar, etc), even if they don't use them.  If not, you will get errors due to dependancies that aren't obvious.

    Monday, December 1, 2008 12:10 PM
    Moderator
  • Thanks alot matey, will definately give that a go. There seems to be alot of bizzareness in CRM

    Monday, December 1, 2008 12:32 PM