See the Winter '14 release notes about the new User Sharing feature. You will need to make users private and create sharing rules for internal users:
This will enable you to restrict visibility of users within a community.
Communities launched in Summer'13.
Before : Partner and Customer Portals
Now : Communities with Partner and Customer Licenses
Before : Limited customisation
Now : Pixel perfect customisation, including customisation of login pages. Use of Site.Com as well as VF Pages for Customisation. Also some ability to customise email with branding.
Before : No ...
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.
Sure, you can use the Metadata API. You want the create() call. Here's the sample xml to define the custom object from the documentation:
<?xml version="1.0" encoding="UTF-8"?>
<description>just a test object ...
Two things must happen in order to @mention a community user on a record feed. The record must be viewed and the Chatter post initiated by the internal user in the communities context. In other words, you must be viewing the record with the Community base URL( e.g. https://mycommunity.force.com/recordid ). Second, the visibility of the Chatter post from the ...
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 ...
This is possible with force.com sites .
With force.com sites you can build visualforce pages that can be accessed by an anonymous user .
The other option is to configure a simple web to Lead form your SFDC instance ,where from your website you can capture the leads and have an internal process for creating community users .
As mentioned, these have all been subsumed into Community, the portal to rule them all.
For the curious, here's the lineage.
This was the very first portal. It's main draw is it's FREE. User management is funky (not stored in the User table), and customization is extremely limited.
Partner / Customer Portal
These are the second portal ...
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 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 ...
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-...
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 ...
I'd discourage Portal creation other than in Dev orgs - any new Portal developmnent should stand on the shoulders of Communities instead. If you replace Portal with Community, a lot of the existing documentation holds true.
Also watch out, I don't think you will get a Portal or a Community to live on your Salesforce domain.
Which one of these portals ...
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.
The way I handled this was based on Pat Patterson's blog post "Oauth for Portal Users":
To set this up with the mobile SDK I did the following:
Created a partner portal and assigned the partner portal gold profile to it
Created a force.com site and set up the ...
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.
yes it is possible. You can use following code to activate user.
User u = new User(id='GET_USER_ID');
//To set password
//To send email send True
You can only create Managed Packages from within a Dev Org.
Sign up for one at http://developer.salesforce.com/
You can create unManaged packages in any type of Salesforce org (Production, Sandbox, Dev) which may be what you're looking for. Managed Packages are only required if you want to make an App-Exchange App.
If you are just looking to communicate ...
When I am posting to a record, as an Internal User I am able to @mention a Partner User from the Internal side with no problem. I have to set the "All with Access" option in the lower left corner of the post form field for the Partner to see the post, however.
The Partner User then gets the record post notification and can answer. I see the answer fine and ...
I also created a case through it but I got replied "Have you looked at our partnerships yet? You need to sign up for one in order to list on the AppExchange." and they provided http://www.salesforce.com/partners/isv/program-models/ link.
If you go to the AppExchange Partner Programs Page that's linked from the one you were given, you'll see two options for ...
Salesforce does not allow this change of License Type (from a Partner Portal License (e.g. Gold Partner) to Full CRM), at all, not via the API, not via the UI, not via anything. Peter is correct about the method of changing a user's License type - it is done indirectly through switching to a Profile associated with a given License type. However, this ...
The trick to changing the license of a User record is that actually you will be updating the Profile of the user. You may have discovered already that "License" is not actually a field in the user object, even thought it appears in the User record UI.
You would also need to update the Role, as partner users are assigned roles that sit outside of the normal ...
I'd say it's not possible to do this the way you described it. After moving to communities your partners will have access to Chatter but it will be independant from internal organization's Chatter (let's call it Internal Community). Profiles, Groups, Files and all activity everything is visible only inside a community even if you're a member of all ...
Looks like unless you upload the package and either generate a BETA or a released version for managed package or a valid version for unmanaged package ,they do not appear .
Strongly recommend that you click on the upload button and generate a version and then it should appear in your organisation in publisher console .
While we thought this was a dev org it was actually a Partner Portal org which expires after 1 year. We filed a case on the partner portal and a representative there extended the org for another year. We're still trying to find a more permanent solution so we don't have this issue again next year.
We use our ISV edition as our main Salesforce org and have never had any license issues. We haven't needed to go the partner portal route, but we do have a customer portal and we just called the AE and purchased the licenses. We've also purchased a number of service cloud and content licenses in the same way.
The ISV edition is simply an enterprise ...
Attachments from portal user emails are not stored apparently due to storage constraints.
Possible workaround using APEX:
Ok, after much head scratching I've found a fix for my own question. In the off chance someone has a similar issue, where an email as part of the approval process uses visualforce components which the user running the test cases as fails in eclipse, but not anywhere else.. Anyway.
The fix for this issue was to grant the partner portal profile which is used ...