Profiles

Use profiles to configure objects, fields, and object views. When you change a setting in a profile, the change is dynamic and the change is immediate. Reports can be added to profiles.

Each user has one or more profiles available to them for their logon session.

You can use profiles to restrict the object types that individual users can view. You can also define the fields in each object that are visible to them. If an object type is absent from a profile, that object type is hidden from users of that profile. You can also assign reports to a profile.

Create profiles by cloning them from existing profiles, then modifying the new profile. A standard profile, called Default, is provided. You can use it as a template to create other profiles. The profiles that you create and assign to users are standalone. No inheritance occurs from one profile to another profile, including the Default profile.

When you associate a profile to a group, all users in the group have that profile added to their Allowed Profiles list. The profile is stored with the user, not the group. If a user is later added to the group, they will not be assigned the profile that was earlier assigned to the users of the group.

You can also designate any profile as the default profile or fallback profile. For more information, see Setting a default or fallback profile.

You can associate available objects with any profile and disassociate them later. However, each profile contains a group of required objects that you cannot disassociate from the profile. The following table lists these required object types: