Salesforce Advanced Admin flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Organization-Wide Defaults

OWD settings define the baseline record access users have to records they do not own, using Private, Public Read Only, or Public Read/Write; other sharing tools can only relax them.

Role hierarchy access

Users positioned above a record owner in the role hierarchy receive the same access to that record as the owner; users in sibling roles receive no access through the hierarchy.

Permission set groups

A permission set group bundles multiple permission sets into one assignment and can mute selected permissions inside them, delivering job-based access without editing profiles.

Most permissive FLS

When a user's profile and permission sets disagree on field-level security, access is granted if any one of them allows it, so the most permissive setting determines the result.

Restriction rule

A restriction rule filters which records a user can access in Lightning Experience using criteria; it can only narrow access already granted, never widen it.

Master-detail relationship

A master-detail relationship makes child records inherit the parent's ownership and sharing, deletes children when the parent is deleted, and enables roll-up summary fields.

Roll-up summary field

A roll-up summary on a master record aggregates related child records using COUNT, SUM, MIN, or MAX with optional filter criteria, and requires a master-detail relationship.

Custom metadata vs custom settings

Custom metadata type records are deployable through change sets and packages and support relationships; custom setting values are not deployable and must be recreated manually.

Dependent picklist

A dependent picklist filters its options based on a controlling field; the controlling field may be a checkbox or picklist but never a multi-select picklist.

Hierarchy custom setting

A hierarchy custom setting stores values at organization, profile, and user levels, and the most specific level defined determines the value returned at runtime.

Setup Audit Trail

Setup Audit Trail logs configuration changes such as permission edits and deployments, showing the 20 most recent entries in the UI and up to six months as a download.

Field history tracking

Field history tracking records changes to selected fields, up to 20 fields per object, retaining data for 18 to 24 months depending on edition before it is purged.

Login history retention

Salesforce retains login history covering the previous six months, including IP address, login type, status, and client, and lets administrators download it as a CSV.

Event Monitoring

Event Monitoring is a paid add-on that captures API, page view, and login events; logs are viewable in-app for 30 days and exportable for up to one year.

Data Loader capacity

Data Loader can process up to 5 million records in a single insert, update, upsert, or delete operation, sending them through the API in batches of 200 by default.

Import Wizard limit

The Import Wizard processes up to 50,000 records per run, supports only selected objects such as accounts, contacts, leads, and custom objects, and cannot be scheduled.

Recycle Bin retention

Records deleted in Salesforce stay recoverable in the Recycle Bin for 15 days; after that period they are permanently removed unless a backup export exists.

Ownership skew

Ownership skew occurs when a single user owns more than 10,000 records of an object that contains more than 10,000 records, slowing sharing recalculation and query performance.

External ID upsert

An external ID field stores a unique identifier from an outside system, letting Data Loader or the API upsert records and relate them without knowing Salesforce record IDs.

Before-save flow

A before-save record-triggered flow runs before the record is committed and updates only the triggering record's fields without extra DML, making it faster than an after-save flow.

Order of execution

On save, Salesforce runs before-save flows, then before-save Apex triggers, then system validation and custom validation rules, then after-save flows and after-save triggers.

Flow fault path

A fault path is attached to a flow element to catch runtime errors, letting the flow log the failure or create an error record instead of stopping and rolling back.

Scheduled-triggered flow

A scheduled flow runs at a configured start time and frequency against records returned by its filter conditions, and it must be activated before the schedule takes effect.

Workflow rules retirement

Salesforce is retiring workflow rules and Process Builder; new automation should be built with Flow, and existing rules should be migrated before support ends.

Change set direction

Change sets deploy from a sandbox to production or between sandboxes linked by an authorized deployment connection, and they cannot delete components in the target org.

RunLocalTests test level

The RunLocalTests test level runs all tests in the org except those from installed managed packages, and it is the standard choice for production deployments.

Partial Copy sandbox

A Partial Copy sandbox contains all metadata plus a sample of data defined by a sandbox template, holds up to 5 GB of data, and can refresh every 29 days.

Destructive deployment

Removing metadata from a target org requires the Metadata API with a destructiveChanges.xml manifest, because change sets cannot delete components during deployment.

Case assignment rules

Case assignment rules route new cases to users or queues based on criteria; only one rule can be active at a time and its entries are evaluated in order.

Lead conversion mapping

Converting a lead creates or matches an account and contact and optionally an opportunity, mapping standard and custom lead fields onto those new records.

Entitlement milestones

Entitlement milestones define service-level targets on cases, such as first response and resolution times, and are applied through entitlement processes tied to entitlements.

Omni-Channel routing

Omni-Channel pushes work items to agents based on routing configuration, capacity, skills, and presence status instead of leaving them in a queue to be claimed manually.