• Timothy O'Connor 1
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 1
    Replies
My parent company is sharing a single Salesforce.com organization amongst a large number of smaller sub-companies. Most of what they are using is straight out of the box. When modest changes are proposed, for example to add a new field to the Opprtunities application, that proposal is reviewed and approved by a "Salesforce Administrator" within each of the sub companies. This makes sense since the transparency that sharing accounts, leads and opportunites across the entire larger organization brings is desirable. However, some of the smaller sub-companies now wish to begin developing custom applications, and it would not be desirable to share those applications across the entire larger organization. Each sub company has concerns with having their own development, test and UAT sandboxes as well. Is there a model for this type of situation?
My parent company is sharing a single Salesforce.com organization amongst a large number of smaller sub-companies. Most of what they are using is straight out of the box. When modest changes are proposed, for example to add a new field to the Opprtunities application, that proposal is reviewed and approved by a "Salesforce Administrator" within each of the sub companies. This makes sense since the transparency that sharing accounts, leads and opportunites across the entire larger organization brings is desirable. However, some of the smaller sub-companies now wish to begin developing custom applications, and it would not be desirable to share those applications across the entire larger organization. Each sub company has concerns with having their own development, test and UAT sandboxes as well. Is there a model for this type of situation?
My parent company is sharing a single Salesforce.com organization amongst a large number of smaller sub-companies. Most of what they are using is straight out of the box. When modest changes are proposed, for example to add a new field to the Opprtunities application, that proposal is reviewed and approved by a "Salesforce Administrator" within each of the sub companies. This makes sense since the transparency that sharing accounts, leads and opportunites across the entire larger organization brings is desirable. However, some of the smaller sub-companies now wish to begin developing custom applications, and it would not be desirable to share those applications across the entire larger organization. Each sub company has concerns with having their own development, test and UAT sandboxes as well. Is there a model for this type of situation?