A user profile is a set of permissions for objects, page layouts, and application access and functions. It can be created for single locations or regions in a multi-location organization. Individual users are assigned to a profile, and get their permissions from the profile.
Permissions are required to work in the Setup.
A profile is a convenient way of creating a group of permissions that can be applied to many users. This way it is simple to change a set of permissions for all the users in a particular profile, and simple to add and remove users from a profile, rather than having to manage permissions for all users individually. This makes it easy to implement organization wide policies on use of and access to information.
There are three types of profiles, User, Member, and Public.
User profiles are for people who log into and work with the application directly, such as administrators, management, employees, etc.
Member profiles are for contacts in your application. These could be members, customers, vendors, contractors, etc. They can log in as members and see only their specific information and have whatever access you give them.
Public profiles allow you to expose information to anyone at all. This could be to do things like post schedules, running on online Store, show news and information, make documents available, etc.
There are three default profiles for every location.
GlobalAdmin: This profile has the most permissions. A user with this profile can work in the Setup, see all records, and perform all tasks across all locations. Although the GlobalAdmin shows up for each location it still has access to all locations. This profile should only belong to application administrators. Setup functionality includes import and export, creating and working with objects, assigning permissions, creating users, setting application default information, etc.
Administrator: This profile is restricted to it's location. It has access to all records in that location. It does not have access to the Setup.
Everyone: This defines a minimum set of permissions that apply to all users (but not to Member or Public profile users). For example, if the Everyone profile has View permissions on the Contact object, all other profiles will have View permissions on Contact even if it is not explicitly granted. However if other profiles have explicit permissions for Contact, they will override the Everyone profile.
A person working with the application (user) needs to have at least one profile. You can create a profile for:
Single location Users. This profile belongs to one Location only. Single location organizations create this type user of profile automatically. A user can only have one profile.
Multiple Location Users. A user can have more than one profile. They can only have one profile in each location. You can create profiles for each location, and you can create organization profiles that apply to regions and all locations in that region. The advantage of an organization profile is that it can be applied to and managed for all locations in a region. It simplifies setting up and editing profiles that are common to many locations in the organization.
Members. These are contacts in your application. When a contact is given a Member profile, you can give them access to their own information and other specific information that you determine. For example, customers could manage their own billing information, book their own appointments, place orders, etc. Members need to login to see member information.
The Public. Anyone can see the information. It can be used with applications such as online booking or a Store that is available to everyone from a web page.
Video Help |
Create a Multi-Location or Regional Profile
