I believe what you are looking for is Super User access:
Super User Access
Users can be assigned super user access to give them access to data
owned by other users belonging to the same role or those below in the
hierarchy. For example, a Partner Manager with super user access can
see data owned by other users in the Partner Manager role and ...
There are no technical restraints regarding the ten object limit. This is actually mentioned in the documentation somewhere. However, if salesforce.com finds out (however that may be), you would be in violation of your contract and at risk for contractual breach.
In theory, this means you'd be forced to pay for the more expensive licenses that you would ...
Two important revisions to communities have occurred since I wrote this answer that should be considered. First is that User Sharing and visibility restrictions on the User Object in an Org are now in place (SU 15 as I recall). This impacts SF Users visibility to other users both inside an Org and within an Org's Customer Community.
The 2nd ...
Setup -> Customize Communities -> Manage Communities
Then press the 'Edit' link left of the Community
Then add the profile/permission set to the Members using the 'Members' button at the top left of the menu.
What you're attempting to create are Criteria-Based Sharing Rules. Unfortunately, you can't share records with your partners using criteria-based sharing. Instead, you can only share records based on their Role, not values in the record itself unless you use Apex Managed Sharing.
In order to share records with Partners in the Community based on record ...
Each Partner Community user associated with the same account gets a unique Role. When a Partner Community user registers from say, Acme Widgets, that user gets the role Acme Widgets User or something of the sort. Every other user who registers related to the Acme Widgets account also gets that role. Users related to other accounts get their own unique role ...
Partner portal users also have access to Community So, it is better to filter a query by Community license:
This will return all users who have a profile with license of community.
List <User> communityUsers = [SELECT id, Name FROM User WHERE Profile.UserLicense.Name='Partner Community' OR Profile.UserLicense.Name='Customer Community'];
Two Factor Authentication is supported for Community Users as pointed out by Rob Cowell.
For standard user license type, you my be accustomed to enabling 2FA via the System Permission Two-Factor Authentication for API Logins and Two-Factor Authentication for User Interface Logins. However, you might not see these options for community profiles.
Per Set Two-...
There is a standard field on Task/Event called Public, which is not visible by default, not even for System Administrators. The value of this checkbox needs to be true to make the event visible for external users in a community.
Below are the answers that I can provide you with:
Every Community User will have both a User record and a Contact Record. All Community Users have profiles. Only Partner Users have Roles.
Will you need to purchase 10,000 licenses? Not necessarily. You'll need to contact your Account Representative to discuss your options once you determine your needs for ...
When you select a MyDomain in production, Salesforce will automatically select domains for sandboxes based on the Sandbox name. That is, if you select mydomain.my.salesforce.com for Production, then your QA Sandbox should have the domain mydomain--qa.my.salesforce.com.
You can find more information about this here.
To that end, you are probably better off ...
There's a special one-to-one relationship between a Community and a Force.com Site. It's actually the associated Site entry that holds the Home Page and enabled Visualforce Pages.
The public home page needs to be accessible by "[Your Community Name] Guest":
go to Setup > Develop > Sites
click "[Your Community Name] Guest"
hit the Edit button,
in 'Active ...
You need to enable Communities inside setup before this option appears.
This guide all all the details: http://help.salesforce.com/help/pdfs/en/salesforce_communities_implementation.pdf
Ensure that your organization has Communities licenses. From Setup, click Company Profile > Company Information
From Setup, click Customize > Communities > Settings.
Here are 3 links you may find more helpful than what you've already referenced Uwe.
I'm including the 1st one because you're an ISV.
OEM User License Comparison.
Getting Started With Communities.
Salesforce Communities Managers Guide.
These seem to be the most comprehensive in terms of explaining the features available that can be enabled in ...
You are correct, Two-Factor Authentication is not available for users with a Partner Community or Customer Community license.
However, there is a no-code workaround: you can implement Two-Factor Authentication for Community Users by creating a custom Login Flow. Login Flows override the default Salesforce login screen, so that your users are taken through ...
At the time of writing (Mar 2016), I believe Two-factor is available for Community Users, based on what I'm seeing at https://help.salesforce.com/HTViewHelpDoc?id=two_factor_auth_for_sso_and_saml.htm&language=en_US
However, your process allows for a far greater degree of customisation, so upvoted accordingly.
Here's how they seem to be defined as of March 2017:
Communities - Sub-domain sites built with Community Builder (Lightning), standard Salesforce UI (Tabs), or custom Visualforce.
Community Builder - A UI for click-and-drag construction of community pages.
Site.com Studio - Replaced by Community Builder (except for a couple features that take you back to ...
The process is very much similar to how you set up for Internal Users except that you need to replace with Community URLS .
Lets look at step by step the mechanism to accomplish the same .For simplicity I am taking another winter 17 pre release org as a SP (Service Provider)
Set Up a Partner Community in Salesforce(This is your IDP org) .Not going ...
When the org wide sharing setting for an object is set to Public Read/ Write, it does not allow reports for the object to be viewed via the partner portal for security reasons.
The workaround for this limitation is to change the org wide sharing settings to Private.
Please go to mentioned link for details.
The list of functions refer to API calls, not Apex objects. There are plenty of objects that show as CRUD or so in the documentation, but will not work in Apex. Instead, you would need to query an existing record and use that in your test. Objects that are not writable in Apex are typically queryable without the use of @isTest(SeeAllData=true).
Partner Communities licenses have access to the full sharing model, while Customer Communities licenses are limited to sharing groups and sharing sets. What that enables in your scenario, is the ability to make the User object private, and therefore restrict the visibility of partner users and their chatter activity from each other in the same community.
A community user can be a portal user. Communities supports several different user types (standard, portal, etc.). The same organization can have a community and a portal running side by side with the same user being able to login to both.
It sounds like what you want to know is "How can I tell if I'm in a community or not"?
To do that, you can use this ...
Support organization has the ability to change the force.com domain name with the proper validation. You can log a case. Keep in mind any domain name change might take up to 24 hours to be effective and the old domain name won't be valid.
I got the reason why my custom error page was not loading, along with assigning custom VF pages under site error page we also need to enable a setting under community preferences.
Thanks all for your comments and suggestions.
Solution seems to be a bit more complicated (and more custom than you'd expect)
Answer based on this document: Code implementation considerations when using custom Login, Landing or Authentication pages for Salesforce1 Communities
STEP 1 the controller apex class that gets the landing page after login should have the following code added:
Install the LMA in your production org. This is necessary because the LMA will create leads for you as your clients install or try out your app. If you put this in your developer org, you may run out of storage space or might even accidentally create a dependency in your app on the LMA, which means your package could no longer be installed by clients.
$A.getCallback needs a function; instead, you're calling a function and returning a null value. It's also not appropriate here, because you're not using a callback at the point you're trying to use $A.getCallback; you want the code in the helper to trigger immediately.
Your code should be simply:
helper.getLazyResponse(component, node.data.uri, cb);
Refer Communities User Licenses
Partner Community License:
A Community member-based license works like a standard Salesforce internal license: external users with a member-based license are able to access a community as many times as they want. The only difference is that external users do not have access to the internal org. Login-based licenses are a ...