A Profile is given access to selected application suites, so that the users in that profile will only have access to those selected applications from all of the available applications.
Permissions are required to work in the Setup.
These Profile permissions allow you to control what applications the users can see and work with. For example, sales people would have access to the CRM application to work with contacts, but not necessarily to the Billing application. You can also set the default application that the Profile's users see when they first log in. This would be the application that is visible in the Application Suite selector at the bottom of the window.
When you have assigned the applications and selected the default application, click Save. A Profile must have at least one application assigned to it (if there is only one assigned application, that is also the default application).
Application assignments are different than object permissions. Object permissions are assigned to a Profile from the Permissions tab, under the Object Service listing. This gives the profile permissions on an individual object only. An application is made up of (usually) more than one object, working with each other. For example, the CRM application has objects for Contacts, Leads, Opportunities, etc.
If a profile has permissions for an application, but does not have permissions for one or more of the objects in the application, the users in that profile will not see those objects when they use the application. For example, if a profile had permissions for the Billing application, but not for the Invoice object, the profile users could see and use everything in the Billing application except for the Invoice object.
If a profile has permission for an object, but not for one or more applications that use the object, the results depend on the application being used. For example, if the user has permissions for the Invoice object but not for the Billing application, they will not see the Invoice object. If there is another application that uses the Invoice object, the user will be able to see the Invoice object in that application.
When setting Profile permissions it is a good idea to consider what sort of permissions are appropriate. What do you want the users of that profile to be able to see and do, and also not see and not do. For example, if you do not want users in the profile to see certain objects at all, it is best to make sure the object permissions on the Permissions tab (Object Services list) are correct; then set the application permissions. If they do not have object permissions, they can not see or use the object at all, regardless of the applications they have access to.
Working with Profiles
Permissions
Did you find what you were looking for? Yes No
Did this help you? Very Helpful 5 4 3 2 1 Not Helpful
How can we improve this topic?
Send Feedback: