Submitted via MS WhiteSpace Program - #4172
In many of the CRM implementations, Customer uses only some of the OOB activity types. Customer often raises the request to remove the unused activity types from the ribbon and menus. CRM should provide the flexibility to configure the activities that need to be shown in the Ribbon/menus or provide separate access privilege for each activities so that each activity type can be managed individually.� Now there is no supported way to show/hide the activity type based on role or usage of activity types in the Organization.
Comments
Thank you for your feedback. Currently this is not in our immediate roadmap, however, we are tracking it and if we indeed get more feedback and votes, we may consider it in the future
Category: Unified Experience: Search, navigation and performance
Definitely agree with Adam on this. As it stands, custom activities can hardly ever be used in real life scenarios as they would unnecessarily clutter up the UI in places where you don't want to see them or for people who have no use for them.
Category: Unified Experience: Search, navigation and performance
Privileges per separate activity would be useful, especially for custom activity types - often the design decision has to be to create a non-activity to allow segmentation of access even for something which 'feels' like an activity and has a natural lifespan and would benefit from all the standard fields for planned/actual start/end (eg custom entity for Project task, only used by project stakeholders). Extending this to OOB as well would be great - do we really want to see Fax all the time?
Category: Unified Experience: Search, navigation and performance
Administrator
Thank you for submitting your idea to our ideas portal. We appreciate your contribution and the time you took to share it with us. We have shipped many enhancements since this idea was posted and it is likely that it has been resolved. If not, kindly reopen. Thank you again for your continued support.