You need to sign in to do that
Don't have an account?
Insufficient Privileges, cannot send email in force.com free edition.
I've checked the document and it is said that with the "Send Email" permission, user can send email by click Send An Email on the Activity History related list of a record.
I'm using an user with the "Send Email" permission enabled. The user license is force.com free. I clicked the "Send an Email" button on one of the custom record and got the "Insufficient Privileges" error.
Following are the details form the help document. Thanks!
Sending Email
Available in: All Editions except Database.com |
User Permissions Needed | |
To send emails: | “Send Email” |
To create an organization-wide address: | “Modify all Data” |
To send email to a contact, lead, person account, or other user:
- Click Send An Email on the Activity History related list of a record. Or, from a case, click Send An Email or Reply from the Email related list. This option is available only to organizations using Email-to-Case or On-Demand Email-to-Case.
I finally find something about the issue...
Users with the Force.com - Free User profile and license receive an Insufficient Privileges error when clicking the "Send Email" button on a record detail page. This appears even when the "Send Email" profile permission is granted.
This error message is correctly displayed for Force.com - Free User licenses. To use the send email functionality, access to the contact object is required. Because Force.com - Free licenses are platform only licenses, they do not include any access to standard objects. The solution would be to utilize a license that does have access to the contacts object.
All Answers
I have use force.com licences and for sure you can send emails.
Look at the user permissions, is he/she the owner of the contact?
How are your org wide default settings?
are contacts read only? or controlled by parent ?(account)
Check your sharing settings, set up - administration set up - security controls - sharing settings.
Did you try to modify the contact record login as this user?
Hi Depton,
Can you please let me know how your profile is configured?
I've enabled all admin permissions and general user persmissions, but still failed...
Administrative Permissions
API Enabled
Manage Public Reports
Edit HTML Templates
Manage Public Templates
Manage Dashboards
Password Never Expires
Manage Data Categories
Schedule Reports
Manage Data Integrations
Send Outbound Messages
Manage Dynamic Dashboards
Tag Manager
Manage Email Client Configurations
Transfer Record
Manage Letterheads
View Data Categories
Manage Public Documents
View Setup and Configuration
Manage Public List Views
General User Permissions
Create and Customize Reports
Mass Email
Drag-and-Drop Dashboard Builder
Report Builder
Edit Events
Run Reports
Edit Tasks
Send Email
Export Reports
Show Custom Sidebar On All Pages
Mass Edits from Lists
View My Team's Dashboards
Hi,
Not sure if this would help, my lincence is Salesforce Platform, so users can only see contacts, accounts, docs and ideas
and then all custom objects....
in the profile there are 2 permissions you need to enable
general user permissions section -
Edit tasks
Send Email
I have sent you a private message in case you want me to help you f urher.....
Is difficult to know the reason, there are a few things to check......
but I´d say that user permissions via roles, org wide default and profile permissions are the things to check.....
you can log a case to salesforce support also....
:))
Thanks, I've logged a case to saleforce.
I finally find something about the issue...
Users with the Force.com - Free User profile and license receive an Insufficient Privileges error when clicking the "Send Email" button on a record detail page. This appears even when the "Send Email" profile permission is granted.
This error message is correctly displayed for Force.com - Free User licenses. To use the send email functionality, access to the contact object is required. Because Force.com - Free licenses are platform only licenses, they do not include any access to standard objects. The solution would be to utilize a license that does have access to the contacts object.
Make sure the user has access to the Contact. Found an issue where a contact on a case was created without an account by a user. Once account was added access to contact on Case was enabled and resolved the error.
The fix: