Salesforce admin Flashcards
What is a fiscal year in Salesforce company settings?
A fiscal year in Salesforce is a 12-month period used to define the financial reporting cycle for a company.
What are business hours in Salesforce company settings?
Business hours in Salesforce are the hours of operation for a company and are used to calculate metrics like response time.
What is currency management in Salesforce company settings?
Currency management in Salesforce allows a company to set up multiple currencies and exchange rates for global operations.
What are default settings in Salesforce company settings?
Default settings in Salesforce are the system-wide settings that define the behavior and appearance of the platform.
What are UI settings in Salesforce?
UI (User Interface) settings in Salesforce control the look and feel of the platform, such as theme, color, and branding.
What is the App Menu in Salesforce?
The App Menu in Salesforce is a customizable menu that displays apps and objects a user has access to.
What are List Views in Salesforce?
List Views in Salesforce are customizable views that display a subset of records based on specific filter criteria.
What are Global Actions in Salesforce?
Global Actions in Salesforce are buttons that allow users to perform quick actions, such as creating a new record, from anywhere in the platform.
What is the Lightning App Builder in Salesforce?
The Lightning App Builder in Salesforce is a declarative tool used to design and customize Lightning Experience apps and pages.
What is the difference between a Standard and a Custom Profile in Salesforce?
In Salesforce, the terms “Standard Profile” and “Custom Profile” refer to different types of user profiles that can be created and assigned to users within the organization. Here’s an explanation of the difference between the two:
Standard Profile: A Standard Profile in Salesforce is a pre-defined profile that comes with the system and is available by default. These profiles are created by Salesforce and are designed to provide common sets of permissions and access rights for different types of users. Standard Profiles include profiles like System Administrator, Standard User, Marketing User, and many others. Each Standard Profile has a specific set of permissions and access settings that determine what actions and data users with that profile can access or modify within the organization. Custom Profile: A Custom Profile, on the other hand, is a user profile that you create and customize according to the specific needs of your organization. Custom Profiles allow you to define unique sets of permissions, access settings, and record-level security tailored to the requirements of different user roles within your organization. You can create custom profiles based on the existing Standard Profiles as a starting point and then modify the settings as needed. With Custom Profiles, you have more flexibility and control over the permissions and access rights granted to users.
The main difference between Standard Profiles and Custom Profiles is that Standard Profiles are pre-built by Salesforce and come with a predefined set of permissions, while Custom Profiles are created by you and can be tailored to meet the specific needs of your organization’s user roles and business processes.
It’s worth noting that both Standard Profiles and Custom Profiles can be assigned to users in Salesforce based on their roles and responsibilities. Users with different profiles will have different levels of access and permissions within the system.
What are limitations of Standard Profiles in Salesforce?
Standard Profiles in Salesforce have certain limitations that may restrict their suitability for some organizations’ specific requirements. Here are some common limitations of Standard Profiles:
Limited Customization: Standard Profiles come with predefined sets of permissions and access rights that cannot be extensively customized. While you can modify some settings, such as object and field-level permissions, you may not have granular control over all aspects of the profile. This limitation can make it challenging to tailor the permissions to match specific business processes or unique user roles within your organization. Lack of Flexibility: Since Standard Profiles are designed to cater to a wide range of users, they may not precisely align with the needs of your organization. If you require more granular control over access to objects, fields, or specific functionality, you may find the options provided by Standard Profiles to be insufficient. Custom Profiles offer greater flexibility in defining permissions and access settings to match your organization's requirements. Limited Record-Level Security: Standard Profiles often have limitations when it comes to implementing record-level security. While you can control access to objects, fields, and records to some extent, it may not provide the level of precision needed in certain scenarios. For more complex record-level security requirements, such as sharing rules based on specific criteria or complex hierarchies, Custom Profiles combined with custom sharing rules or other advanced features like permission sets may be necessary. Potential Over-Provisioning: Standard Profiles are designed to be broad in their permissions to accommodate a wide range of users. This can result in over-provisioning of permissions, granting users access to more data and functionality than they actually need. Over time, as your organization's requirements evolve, you may find that using Custom Profiles and more precise permission settings allows for better control and security. Limited User Segmentation: Standard Profiles may not offer the ability to segment users based on specific criteria or attributes. For instance, if you want to create different permission levels for users based on their department, location, or other custom criteria, Standard Profiles may not provide the necessary flexibility. Custom Profiles, combined with features like permission sets or user roles, can help you achieve more targeted user segmentation.
To overcome these limitations, organizations often leverage Custom Profiles in Salesforce to create profiles that align with their specific needs and provide more granular control over permissions, access rights, and record-level security.
Cloudy Computing, a US based company, has recently opened a small European office in the UK. The European team is complaining that the timezone and date/time format is confusing. To ensure all users have the correct timezone and formatting, what should the Administrator suggest?
Have each European user change their locale via Personal Settings
Have each European user change their time zone via Personal Settings
As the Salesforce Administrator at Cloudy Computing, you have implemented Login Hours, specifying that users may only log in between 9:00am-5:00pm. If a user is currently actively working on a record and clicks save at 5:05pm, what will happen?
If a user is still logged in to Salesforce when the Login Hours expire, they can continue to view the page they have open, but cannot take any further action. This means that if a user attempts to save a record after 5pm, they will be logged out and any progress (edits) will be lost.
As the Salesforce Administrator, you have created a custom field on the Opportunity object. The field is read only in the field-level security settings. When you add the field to the relevant page layout, you accidentally make the field required. What behavior can we expect in this scenario?
When a user edits the page layout, the field will be read only
The Eastern Sales Team should have read access to Opportunities owned by the Western Sales Team. The sales teams have different roles and the Opportunity OWD is currently set to Private. How could you achieve this requirement?
Create a sharing rule based on role
