My thanks to bigassforce, who found this Salesforce.com Article for me to reference.
Salesforce licenses are designed for users who require full access to standard CRM and Force.com AppExchange apps. CRM apps are anything that requires access to Standard Objects like...
Salesforce Platform licenses are ...
The main difference is the price and the objects you can access. The following help page has more detail:
Authenticated Web Site is the Platform Portal and has read and create access on ideas and questions and answers, and read-only access to documents, knowledge, price books, ...
OEM is an abbreviation for Original Equipment Manufacturer:
An original equipment manufacturer, or OEM, manufactures products or
components that are purchased by another company and retailed under
that purchasing company's brand name. OEM refers to the company that
originally manufactured the product. When referring to automotive
parts, OEM ...
When a sandbox is created from an org with an active managed package license the sandbox will act as if it had a site license. The net effect of this is that all users in the org are automatically and always licensed without having to manage licensing per-user.
I don't know if this behavior is documented but I've seen it time and time again while working ...
1) What is the minimum cost to become partner (ISV/OEM)?
Becoming an ISV partner costs nothing. The tools (all you can eat developer orgs, partner support, technical library, tutorial material, training courses and webinars) are free. Listing an app costs money.
To list on the AppExchange and license your application to Salesforce customers will cost you ...
As of Summer 14, there are 2 new objects which allow you to use SOQL to see which users are licensed for particular Managed Packages: PackageLicense and UserPackageLicense.
UserPackageLicense lets you see which users are licensed for a particular package:
String APP_NAMESPACE_PREFIX = 'skuid';
List<User> licensedUsers = [
I'm not easily finding a confirming link, but your guess is correct - the "Login" licenses are for logins-per-month pricing, and the plain "Community" licenses are for named-user licensing. I just took a training on Communities implementation where this was covered.
[D]o their licenses get removed as well[?]
[D]o we have to manually remove them from each package?
Allow me to explain. The license assignments remain when a user is deactivated. However, you can write a trigger or Process Builder (via a flow) to remove those assigned licenses when a user is deactivated. This is how we keep our license count ...
Here is the nice resource which describes communities licenses in details:
Customer Community and Partner Community licenses are offered as
member-based or login-based:
A user with a member-based license can log in to communities as often
as he ...
A really good breakdown of the difference between OEM and ISV has been posted on Linkedin here and copied below
Key differences: (1) the app creator's contracts with Salesforce and
end users (2) what end users receive. When you sell an app under an
OEM agreement, you are selling the end user BOTH Salesforce Platform
user licenses AND package ...
Apex Code has two modes of operation: "sharing" and "without sharing" modes. While in sharing mode, the user's permissions will have an effect on what they're allowed to do. When using "without sharing," there's virtually no limitation as to what the code can do, including modifying records on an object the user can't even access, etc, as you've found with ...
In addition to what Vivek said, Salesforce licences have much more administrative permissions than Salesforce Platform licences. These include:
- Ability to manage internal users
- Authoring Apex
- Managing Package licences
- Managing sharing
- Managing login access policy
There are many more administrative rights. Go to the profiles and compare ...
If this is a legitimate concern for you, then your best bet is to negotiate an escrow agreement for the source code. It's not unusual in enterprise software to enter into an agreement with a software provider that entitles you to their source code if they go under. But that's a legal agreement that will cost money, so you'll need to negotiate the creation of ...
In my experience building AppExchange apps, in particular working on Skuid, which heavily relies on overriding Salesforce Buttons/Actions with Visualforce Pages, you will have to rely on your users creating some local VF Pages within their local orgs --- otherwise, as you have realized, you are in a Catch-22: you'd think you could just include UserInfo....
The Guest "User license" is designed for public users who access your Site.com or Force.com sites. If Communities is enabled, these users will also have access to public pages in your communities. Site visitors have access to any information made available in an active public site. For each Guest "User license", you can develop one site for your organization....
First, watch this video: Ready to Partner with Salesforce.com (ISVforce or OEM)? (http://www.youtube.com/watch?v=_oV9LthQ5O0)
ISV companies can sell licenses to their own apps (which I would say is the most common - this would be using the AppExchange to sell, say, 5 licenses of a managed package app. With new AppExchange checkout features ...
I asked support nicely for more licenses for the developer org, which they kindly granted, along with:
Partner Developer Edition orgs do come with 20 Salesforce licenses. However due to our new release, a minor bug has caused our Partner Developer Edition orgs to be created with only 2 licenses.
We should have this fixed by early March.
In the ...
Salesforce offers Force.com Light App Licenses that can access up to 10 Light Application Objects for a little bit cheaper than the Force.com Enterprise App License. You can find out a little bit more in the docs but it's best to talk to your AE about licenses that you may need.
This is a type of OEM application where SF allow user to build app and sell it as per there customization.
The AppExchange OEM Edition nevertheless offers developers a proven and secure platform, which allows them to focus on their product innovation without having to worry about the infrastructure. It allows developers to leverage the SalesForce platform ...
Salesforce allows you to build an application, called an OEM application, where your subscribers do not pay salesforce.com directly for licenses, but instead pay the OEM partner directly. In turn, the OEM partner pays a percentage of its license revenue to salesforce.com. Typically, salesforce.com loses a few bucks per license, but is still gaining revenue ...
Loading 10,000 users is the same as loading 1 user. Just map the fields appropriately and upload the records via Data Loader/API/etc. To answer your questions:
What are the steps/or how can we load 10,000 users to salesforce org?
Install Apex Data Loader, create CSV file, upload users to target org.
What kind of permissions or salesforce editions ...
The quick answer: if it appears in the User Logins admin report in Salesforce, it's counted.
The longer answer: yes if someone explicitly signs in multiple times during a session, even when they were already logged in, it is counted. So yes you will need to be diligent about this. If it's a web service, what I would do is make it a term of service that they ...
You need to contact your AE for this pricing information. We are unable to provide you an accurate response. It really varies by customers. When you do an upgrade/contract renewal the AE might throw in say 2 partial sandboxes or something. This really just varies by the Edition you are on (Professional/Enterprise/Unlimited/etc) and your contract size. ...
In general, if a feature license requires you to pay for the license, then the answer comes down to money. Did you buy enough licenses for every user in your org to use that feature.
If the answer is yes then rock on with your bad self. Turn that on for everyone.
If the answer is no then of course, you'll have to be selective.
As to this particular ...
Update: here is a blog-post which best explains the distinctions between the various org types involved in the AppExchange publishing process:
Understanding the AppExchange publishing process, environments, and app lifecycle
As a brief summary, though, here is an explanation of the roles of each type of org:
Managed Package Development Org - you will need ...
You won't be billed beyond the available licences, you're just billed for the licences you have. That said, you may not be using all of your licences if you have deactivated some users and not added new users.
To reduce your licence count your administrator must file a case with support, using "Licence Reduction" as the subject line as shown in this ...
Per the comments on the question, it appears that the solution is that the developer needs to use the Partner WSDL, or generate a new Enterprise WSDL that includes the missing objects for their Sandbox organization.
The User Licenses Overview no longer lists the license type, which may be evidence that they are indeed discontinued. Traditionally, license types that are discontinued are still available to current customers that have those licenses until they expire.
However, there's a new type of license called Platform Portal, whose description starts off as "Platform ...
There is no solution to this since you have consumed all the license that were allocated for your org .
Deactivate the existing users if you are testing your code .
You can also purchase additional license to avoid this .
Your use of salesforce.com is bound by contractual agreements. By intentionally bypassing license restrictions, you are in breach of contract. You may be subject to retroactive license fees, suspension or termination of services, as well as other legal remedies that may arise from breach of contract. While I have not heard of any organization actually ...