Salesforce is split across login "domains." Each domain uses its own username index, which means it's entirely possible to create the exact same user on login.salesforce.com, test.salesforce.com, and prerellogin.pre.salesforce.com, and any other unique login domains that may exist. Note that "My Domain" does not constitute a unique login domain; it still ...
Try this trick from http://www.michaelforce.org/blogView?id=a0D3000000AKmy5EAD for changing a user's email address (works in production too):
If you change the email address AND check the "Generate new
password and notify user immediately" checkbox (all the way at the
bottom of the edit screen) then the email address gets committed right
away, no ...
Platform Change : As of v29.0 you can now query the AuthSession object .
According to the session timeout documentation, the last LastModifiedDate on the AuthSession gets updated when there is activity by the user in the last half of his or her the session.
An approach making use of the above : If you are prepared to reduce the session timeout to 15 ...
The authentication mechanism seems to have a replication delay. Changing your user name results in an email being sent to you:
Dear Mr. User,
Your username has changed.
New username: ABC
Old username: XYZ
The new username may take several minutes to become fully functional.
We recommend you log in with the following link for the ...
I feel like an idiot. The 'Manage External Users', and the 'Edit Self Service Users' are the correct permissions, it just happened that the layout for a particular group of users did not have the button on their layout. Glad it a was stupid silly fix, but definitely feel stupid. thanks all
Standard Profiles which mostly used are:
A profile of which most of the permissions you can't change are standard profiles.
Profile is standard which have Custom Profile label unchecked when you open it.
Also you can differentiate standard and other profile by ...
There are six (6) Salesforce standard user profiles. Additional standard profiles will appear when certain conditions are met within an organization, such as enabling Chatter, Partner Portal, Customer Portal, or Sites. The link posted in the original question does not appear to include all possible profiles that are available. For example, there are legacy ...
To prevent the security question from appearing, you have to reset the password.
It looks like you let a (new) user take the account of another user. That's not a good practice. It's better to disable a user, and create a new account for the new user.
It can't be done. I've had the same problem, your best bet is to start a new managed package.
However, if your App is uploaded to the AppExchange, and your a partner, you can try to contact Salesforce partner support (if your a partner and it is distributed on the AppExchange). Ask them to 'unlock' your package, you will have to have it uninstalled from ...
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 ...
That is not possible. Please refer to this article
Try logging a case.
You can't convert a Chatter Only license or any other standard Salesforce licenses to a Chatter Free license. You can, however, deactivate the Chatter Only user and create a new Chatter Free user with a unique ...
Below the link how to add system admin (yourself) to community to be able to manage it.
What would you accept as an authoritative answer here? Someone internal to Salesforce could look at the underlying implementation and see the why of it. The best I can do is look at the available documentation and WSDLs.
My assumption is that the internal values that Salesforce have for the User Type were manipulated when exposed via the SOAP based api to ...
I think you're looking in the wrong spot. The role that needs to exist is on the owner of the account record, not directly on the community user.
We have a workflow that forces all of our contacts/accounts to have the same user act as the owner and gave that owner a very generic role which allows us to easily create community users via apex.
I can ...
You should be able to populate the fields from an external system without a problem.
However, there's one thing to keep in mind, the community nickname is a unique name used on the salesforce community.
Alias <= 8 chars
Community nickname <= 40 chars
It is not currently possible to create a Workflow to be triggered off the User Record.
Its quite a popular idea, so feel free to promote it :)
You can do this using a trigger on User - the bit to send an email would be easy. Identifying all open records would be slightly more difficult, depending ...
The bottom line is that you can't do this in a reliable way using Apex - we've had a few tries at it. The best we've been able to come up with is a sidebar component that updates a custom field on the user or a related custom object whenever it is rendered. However, given the web nature of the Salesforce UI, you only know what the user is doing when they ...
It says this in the Summer 13 release notes:
"When your organization has Communities enabled, User Sharing lets you control which other users Community members can see. You can control community members’ access to both internal and external users."
But it sounds like there might be an option without communities:
User Sharing for internal users is also ...
You cannot reset the token directly, as the administrator. However, administrators have ways to make this happen. As an administrator, you could:
Reset the user's password, and have them log in; they'll be emailed a new token after setting their password.
Get the user's password, and login as them.
Call setPassword on the user, thus giving you the ability ...
For those that do see it, if you are looking at a dev org created from an existing EE org, you should have it. However, if you are creating a brand new dev org that is not connected/related to an existing EE org, it is not there.
Just to add to @John Thompson's answer, you can add the button that disables the customer user:
This will remove the connection between the user and the contact, and mark the user as deleted.
If you don't have this button - you can add it to your layout from the page layout editor:
After removing the connection between the contact and the user you can ...
EDIT : I read your question as Chatter Groups, whereas you meant Sharing Groups I reckon.
Chatter Groups are in fact restored when you reactivate the User, I've just tried this. Can't remember know why I thought the Chatter Group Memberships were not restored when the User was reactivated.
I don't believe there is way to seamlessly do this.
Seems like there is no work around to Use 'login as' feature with SAML enabled and if there is any, they are considered to Security Holes in the implementation by Salesforce.
I got this excerpt from one of the Salesforce Knowledge base mentioned here http://help.salesforce.com/apex/HTViewSolution?id=000175641&language=en_US
Insufficient Privileges ...
The user name isn't the same as the email address, not does it have to be a "real" email address, so long as it looks RFC 2822 compliant (more or less, anyways).
One typical scenario is to create different user accounts in each org with a common naming convention. Let us say that "John Doe" is a developer that needs multiple developer logins for your ...
It really depends on what the API users are doing to interact with the salesforce system. The enterprise platform licenses have API access, but, if you need to interact with the Opportunity record, for example, they won't work. If they are connecting with the remote system to copy custom object data, then the platform license might work for you.
Here is a ...