Custom Labels and Custom Permissions

import saveButtonLabel from '@salesforce/label/c.Save_Button_Label';

export default class MyForm extends LightningElement {
    labels = { save: saveButtonLabel };
}

<lightning-button label={labels.save}></lightning-button>

A Custom Label is a piece of user-facing text defined once in Setup and made translatable into any language the org supports — importing it from @salesforce/label/c.<LabelName> avoids hardcoding English text directly in a component, which would never adapt for non-English users (Lesson 6 covers internationalization in full).

@AuraEnabled(cacheable=true)
public static Boolean canApproveDiscounts() {
    return FeatureManagement.checkPermission('Can_Approve_Discounts');
}

import canApprove from '@salesforce/apex/PermissionController.canApproveDiscounts';

@wire(canApprove)
canApproveDiscounts;

A Custom Permission is an admin-configurable, custom access flag — beyond standard object/field-level security — that can be assigned to specific users or profiles. There is no direct client-side way to check one from LWC; it must be checked in Apex (via FeatureManagement.checkPermission) and exposed through an @AuraEnabled method, following exactly the cacheable=true/@wire pattern from Module 7.

Hardcoded strings and permission checks baked directly into component logic are both common sources of real production problems — one breaks the moment a non-English user opens the org, the other breaks the moment an admin needs to grant a new team access without a code deployment.