Permissions, Preferences & Licensing Flashcards Preview

SFCC Admin Practice > Permissions, Preferences & Licensing > Flashcards

Flashcards in Permissions, Preferences & Licensing Deck (25)
Loading flashcards...
1

Add-on

An optional extension for an org to supplement the functionality provided by the edition. An org can have multiple add-ons. An add-on includes one or more permission set, platform, or user licenses, or a combination of those.

2

Demo org

A sample org used to demonstrate Salesforce functionality to prospective customers.

3

Developer org

A free, non-expiring org that a developer can use to develop, test, and deploy applications.

4

Edition

A bundle of features and services that comprise the functionality necessary to activate an org. Salesforce offers several editions, which provide varying levels of functionality.

5

License

The contractual agreement between Salesforce and a specific customer, which includes a metadata description of the functionality for the associated Salesforce product that is available to the customer org.

6

License definition

A metadata description of the functionality for a given Salesforce product that is available to a customer org.

7

Permission

A metadata switch, or setting, that configures a particular aspect of product functionality. In general, permissions control access to features, such as Lightning Experience or Chatter, and certain aspects of security. Compare to preference.

8

Permission set license

A license that defines user-level functionality, which can be assigned to supplement the functionality in a user license. A user can be assigned multiple permission set licenses. Note that a permission set license is different from a permission set, defined in the next unit.

9

Platform license

A license with metadata switches, or settings, that control functionality for the org as a whole.

10

Preference

A metadata switch, or setting, that configures a particular aspect of product functionality. In general, preferences define settings that customers can configure, such as time zone or password options. Compare to permission.

11

Product license

An edition or add-on, which bundles together one or more settings licenses and other metadata in a product that the customer can purchase.

12

Production org

Customer’s active org where users access and work with live data.

13

Provisioning

The process of activating licenses and enabling functionality in an org.

14

Sandbox org

A replica of a production org that serves as a staging environment where the customer can test changes without affecting the production org or users.

15

Scratch org

A short-lived deployment of Salesforce that enables developers to emulate different Salesforce editions, features, and preferences. Each scratch org is automatically deleted after 7 days.

16

Setting

A metadata switch in a license that configures a particular aspect of product functionality.

17

Settings license

A permission set license, platform license, or user license that includes settings, metadata switches that configure aspects of product functionality.

18

Trial org

A free org with sample data, designed for prospective customers to evaluate Salesforce before purchasing.

19

User license

A license that defines user-level functionality. Each user is assigned one user license.

20

Platform-level permission

Specify features and capabilities for the org as a whole. Platform-level perms are turned on or off by the provisioning system, based on what a customer purchases. As a customer, you can’t turn platform-level perms on or off.

Examples of platform-level perms include support for creating custom objects or making API requests.

21

Platform-level preferences

Like platform-level perms, these prefs also specify features and capabilities for the org as a whole. Unlike platform-level perms, as an org admin you can turn platform-level prefs on or off, usually through Setup.

Examples of platform-level prefs include language settings and time zone settings.

22

User-level perms

Specify functionality for individual users.

As an admin, you use profiles and permission sets to control which user perms in a license are activated for a given user, so that users with the same license can have different levels of functionality.

23

User-level prefs

Specify personalization choices, such as tab display. Each user can configure user prefs for themselves. (User prefs don’t control functionality related to feature access or security.)

24

Profile

A subset of the functionality defined in a user license or permission set license.
As an admin you assign each user one profile, based on the user’s job requirements.
The functionality in the profile can’t exceed the functionality in the user license or permission set licenses assigned to the user.
Profiles ensure that users have the functionality they need, but don’t have any functionality that exceeds their job requirements.
For example, a user license may provide the capability to read, edit, and delete records, but an assigned profile may only provide the capability to read and edit records. The profile defines baseline functionality for the user, which can’t be revoked as long as the profile is assigned.

Each Salesforce edition includes several standard profiles. Some editions include the option to create custom profiles. The profile defines the baseline access for a user.

25

Permission set

Like a profile, a permission set is a subset of the functionality defined in a user license or permission set license.
But, while a user can have just one profile, each user can be assigned multiple permission sets.
Each permission set can extend a user’s access beyond the functionality defined in the profile. Like profiles, permission sets can’t exceed the functionality defined in the assigned user license or permission set licenses. Salesforce provides standard permission sets, and some editions include the option to create custom permission sets.

So, why would you use both profiles and permission sets? The profile, as we described, defines the baseline access for a user. Permission sets provide a way to layer additional functionality, to supplement the baseline.

With permission sets, as an admin you can grant functional access to a user for specific scenarios, regardless of the user’s primary job function. You can use permission sets to reduce the number of unique profiles you need to create, and to reduce the number of permissions you need to include in the profiles.