Date: Fri, 29 Mar 2024 07:03:41 +0000 (UTC) Message-ID: <868031543.51.1711695821405@ee247a49ef7d> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_50_1940575337.1711695821405" ------=_Part_50_1940575337.1711695821405 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Talk to your AE
This page contains some notes about what I know about licencing at this = point in time, and what is available from publicly accessible sources. It i= s not advice about licencing, and it is not everything you need to know. Yo= u need to talk to your Salesforce Account Executive (AE) about your specifi= c Salesforce Licencing.
I recently had the opportunity to learn a lot more about licencing that = I ever wanted to know. So here are some notes about that. This is not a FUL= L overview of licencing by any stretch of the imagination. Just some points= .
This is a handy starting point but beware, it is a little out of date.&n= bsp;https://docs.google.com/spreadsheets/d/1REUjHOskL7VPFfMqd8ujWkoWFrkmC9D= tqm0viQOb4xc/edit#gid=3D0 - no Employee community and Portals are = not marked as deprecated.
For your reading pleasure - the Master Services Agreement https://www.salesforce.com/assets/pdf/misc/= salesforce_MSA.pdf
ALL of the agreements http://www.s= alesforce.com/company/legal/agreements.jsp
Just beware of where apps are accessing your data, transmitting your dat= a to and storing your data.
From https://appexchange.salesforce.com/= userAgreement my emphasis.
That may result in the disclosure,= modification or deletion of your data by those providers or their app= lications. Further, the AppExchange application provider and its agents and= partners may collect and use, data pertaining to your configuration an= d use of the application. Salesforce.com is not responsible for any tr= ansmission, collection, disclosure, modification, use or deletion of your d= ata, as described in this paragraph, by or through third-party AppExchange = applications or their providers.
Your use of AppExchange applications w= ill be governed by terms you must click-accept during the test drive or ins= tallation process. Please read those terms carefully before accepting them.= If the AppExchange application is provided by us, you may contact us with = any questions about those terms. If the AppExchange application is provided= by another company, then you should contact that company directly with any= questions about those terms.
An OEM application is an application built on top of the force.com platf= orm. It allows companies to build a great application without having to bui= ld all the infrastructure first - it is using force.com as the base platfor= m that handles security, user management, creating and displaying data etc.= Fundamentally there is very little difference between the force.com platfo= rm and Salesforce products like Service Cloud and Sales Cloud. It is more a= round how the products are licenced, and what is included in the bundle cus= tomers pay for.
The force.com platform has standard objects - Accounts and Contacts, Tas= ks, Activities, Chatter, Files and Documents, as most software applications= have something to do with tracking the details of people and connecting wi= th people. OEM developers build on top of this platform by using force.com = Custom Objects.
OEM applications allow application developers to bundle up their customi= sations and sell them together with the force.com platform licencing.
The main thing about an OEM application is the licencing. See OEM Embede= d licences on the Salesforce hel= p site. The OEM Licence, although it gives you the ability to see Leads= , Opportunities, Contracts and Cases expressly prohibits the use of these o= bjects. The OEM Embedded licence is "A full Force.c= om license with contractual restrictions. It prohibits Create, = Read, Update, and Delete on Leads, Opportunities, Cases, Solutions, and Cam= paigns" and "End users can=E2=80=99t develop applications or extend= applications by creating custom objects, but they can have access to addit= ional applications as long as those applications are sold with an embedded = license".
The licencing is controlled by the SFDC Service Agreement that is sold w= ith the OEM package. A quick google search shows some of them https://www.google.com.au/search?q=3D%2= 2SFDC+Service+Agreement%22. Let's have a look in detail at the Financia= l Force agreement. (I chose Financial Force because it is a Salesforce OEM = app).
SFDC Service Agreement Excerpt. Clause 1 (a)
http://www.fin= ancialforce.com/company/cloud-erp/legal/platformtermsofuse-other/ = my emphasis.
Each User subscription to the Reseller= Application shall entitle one User to use the Service via the Reseller App= lication, subject to the terms of this SFDC Service Agreement, together wit= h any other terms required by Reseller. User subscriptions cannot= be shared or used by more than one User (but may be reassigned from t= ime to time to new Users who are replacing former Users who have terminated= employment with You or otherwise changed job status or function and no lon= ger require use of the Service). For clarity, Your subscription to us= e the Platform hereunder does not include a subscription to use the SFD= C Service or to use it in connection with applications other than the Resel= ler Application. If You wish to use the SFDC Service or= any of its functionalities or services, to use another application other t= han the Reseller Application, or to create or use additional custom obj= ects beyond those which appear in the Reseller Application in the form= that it has been provided to You by Your Reseller, visit www.salesforc= e.com to contract directly with SFDC for such services. In the= event Your access to the Reseller Application provides You with access to = the SFDC Service generally or access to any SFDC Service functionality with= in it that is in excess to the functionality described in the Reseller = Application=E2=80=99s user guide, and You have not separately subscribed un= der a written contract with SFDC for such access, then You agree to not acc= ess and use such functionality, and You agree that Your use of such fu= nctionality, Your use of applications other than the Reseller Application, = or Your creation or use of additional custom objects in the Resell= er Application beyond that which appears in the Reseller Application in the= form that it has been provided to You by your Reseller, would be a mat= erial breach of this Agreement.
This means the following:
You can buy a simple Salesforce licence that gives you access to a limit= ed amount of Custom Objects (but not CRM Objects), or a Salesforce.com Sale= s Cloud or Service Cloud licences.
It is all about the Custom Objects. You can't create your own Custom Obj= ects without additional licencing, but it looks like you can install as man= y third party apps as you want. The custom objects contained in a = managed package publicly posted on the AppExchange don't count against the = limits for your Salesforce Edition. So, just beware of Unmanaged Packages and packages that are listed as = Private (eg this as an example) - it says = what they are on the details tab of the AppExchange listing.
The Chatter Plus licence gives 10 cust= om objects but the Salesforce App Bundle&= nbsp;gives 200 custom objects for AU$110/user/month. If you are wanting to = create a few custom objects, or install unmanaged packages then going with = the App Bundle means that you don't have to obsessively worry over exactly = how many Objects each user may have access to. Note however, that the Chatt= er Plus or the App Bundle does NOT entitle users to use Standard "CRM" Obje= cts like Opportunities, Leads, Cases, Contracts etc. You need a f= ull Salesforce.com licence for that.
Similar to OEM licencing, it is all ab= out the custom objects. The use of the Standard Salesforce objects like Opp= ortunities, Leads, Cases, Contracts in Salesforce is not allowed
http://www.salesforce.com/au/cr= m/editions-pricing-platform.jsp
This is great if you are not a Sales-focused company and want to develop= your own in-house apps in Salesforce.
But remember, as Steven Herod says, "if it looks like a duck and= quacks like a duck it's a duck". So don't try to re-create Opportunities j= ust to save money.
You can still install AppExchange Apps.
I look at this type of app as Dicing up the Salesforce platform - you ca= n have all the features of Salesforce except the chunk of standard objects.= (in comparison, I think of Communities licences as Slicing the Salesforce = platform - you can have access to all the standard and custom objects you w= ant to give your customers and partners, but only limited records). = p>
I won't delve into communities licencing just yet.
Here is a great post to explain some of the high level details. Salesforce Standard Object Access by Community or Portal license = type - LimitException
And the Salesforce comparison of Communities licencing = https://help.salesforce.com/apex/HTViewHelpDoc?id=3Dusers_license_types_com= munities.htm&language=3Den_US