1.What is Salesforce?
Answer: Salesforce.com is a cloud computing company headquartered in San Francisco, California. It’s founded in 1999. It’s founder is Marc Benioff and Parker Harris . It is best known for its customer relationship management (CRM) product. Salesforce help users handle all of their business needs like managing marketing campaigns, analyzing performance, and tracking spending and sales. Salesforce works on cloud computing technology. In Salesforce we pay only for what we use.
2.What is Force.com?
Answer: Force.com = Platform-as-a-Service (PaaS) offering from the same company that allows you to build your own applications and/or customize the standard applications. Salesforce.com is a company that offers pre-built applications under “Sales Cloud”, “Marketing Cloud”, “Service Cloud” etc. Force.com is a Platform as a Service (PaaS) product designed to simplify the development and deployment of cloud-based applications and websites.
3.What is cloud computing?
Answer:Cloud computing is a general term for anything that involves delivering hosted services over the Internet. These services are broadly divided into three categories: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS) and Software-as-a-Service (SaaS).
4.What is Profile in Salesforce?
Answer: When we create users, we assign a profile to each user. Profiles define how users access objects and data, and what they can do within the application. A profile is a group/collection of settings and permissions that define what a user can do in salesforce. A profile controls “Object permissions, Field permissions, User permissions, Tab settings, App settings, Apex class access, Visualforce page access, Page layouts, Record Types, Login hours & Login IP ranges.
Remark: In Enterprise, Performance, Unlimited, and Developer Edition organizations, you can use standard profiles or create custom profiles. In custom profiles, you can edit all permissions and settings except the user license. In Contact Manager, Group, and Professional Edition organizations, you can assign standard profiles to your users, but you can’t view or edit the standard profiles and you can’t create custom profiles. Every profile belongs to exactly one user license type. Standard profiles are included with Salesforce. Object-level and user permissions cannot be changed on these profiles. Standard profiles cannot be deleted.Custom profiles are created by an administrator and can be fully customized. Custom profiles can be deleted.
Standard Profiles which mostly used are:
5.What is Role in Salessforce?
The user’s Role determines what data the user can see. Roles give an organization the ability to control access to information. Salesforce’s Role hierarchy is structured as a tree: users can see data only for their branch, unless otherwise shared. Salesforce offers a user role hierarchy that you can use together with sharing settings to determine the levels of access users have to your organization’s data. Depending on your organization’s sharing settings, roles can control the level of visibility that users have into your organization’s data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless your organization’s sharing model for an object specifies otherwise.
Remark: Specifically, in the Organization-Wide Defaults related list, if the Grant Access Using Hierarchies option is disabled for a custom object, only the record owner and users granted access by the organization-wide defaults receive access to the object’s records.
Roles also determine the access users get to cases, contacts, and opportunities regardless of who owns those records. The level of access is specified on the Role Edit page. For example, you can set the contact access such that users in a role can edit all contacts associated with accounts they own, regardless of who owns the contacts. Similarly, you can set the opportunity access such that users in a role can edit all opportunities associated with accounts they own, regardless of who owns the opportunities.
6.What is Page Layout?
Answer:Use field-level security to control the access that users have to certain fields. Additionally, use page layouts to control the layout and organization of detail and edit pages in Salesforce a user’s sees.Customize search layouts to change which fields display in search results and the buttons that display on list views. Control which fields, related lists, and custom links users see, on detail and edit pages only.Control which standard and custom buttons display on detail pages and related lists.Determine whether fields are visible, read only, or required, on detail and edit pages only.
7.What is Sharing?
Answer: Make automatic exceptions to your organization-wide sharing settings for defined sets of users. use sharing rules to extend sharing access to users in public groups, roles, or territories. Sharing rules can never be stricter than your organization-wide default settings. They simply allow greater access for particular users. Sharing enables record-level access control for all custom objects, as well as many standard objects (such as Account, Contact, Opportunity and Case). Administrators first set an object’s organization-wide default sharing access level, and then grant additional access based on record ownership, the role hierarchy, sharing rules, and manual sharing. Developers can then use Apex managed sharing to grant additional access pro-grammatically with Apex.
Salesforce has the following types of sharing:
Force.com Managed Sharing :Force.com managed sharing involves sharing access granted by Force.com based on record ownership, the role hierarchy, and sharing rules:
Record Ownership:Each record is owned by a user or optionally a queue for custom objects, cases and leads. The record owner is automatically granted Full Access, allowing them to view, edit, transfer, share, and delete the record.
Role Hierarchy: The role hierarchy enables users above another user in the hierarchy to have the same level of access to records owned by or shared with users below. Consequently, users above a record owner in the role hierarchy are also implicitly granted Full Access to the record, though this behavior can be disabled for specific custom objects. The role hierarchy is not maintained with sharing records. Instead, role hierarchy access is derived at run time.
Sharing Rules: Sharing rules are used by administrators to automatically grant users within a given group or role access to records owned by a specific group of users. Sharing rules cannot be added to a package and cannot be used to support sharing logic for apps installed from Force.com App Exchange. Sharing rules can be based on record ownership or other criteria. You can’t use Apex to create criteria-based sharing rules. Also, criteria-based sharing cannot be tested using Apex.
Manual Sharing: User managed sharing allows the record owner or any user with Full Access to a record to share the record with a user or group of users. This is generally done by an end-user, for a single record. Only the record owner and users above the owner in the role hierarchy are granted Full Access to the record. It is not possible to grant other users Full Access. Users with the “Modify All” object-level permission for the given object or the “Modify All Data” permission can also manually share a record. User managed sharing is removed when the record owner changes or when the access granted in the sharing does not grant additional access beyond the object’s organization-wide sharing default access level.
You can control who sees whom in the organization, including internal and external users, if your organization has User Sharing enabled. Manual sharing and sharing sets provide additional access beyond the organization-wide defaults and sharing rules. External users, such as high-volume portal or community users (HVPU), don’t have roles and can’t be used in sharing rules.
Apex Managed Sharing: Apex managed sharing provides developers with the ability to support an application’s particular sharing requirements pro-grammatically through Apex or the SOAP API. This type of sharing is similar to Force.com managed sharing. Only users with “Modify All Data” permission can add or change Apex managed sharing on a record. Apex managed sharing is maintained across record owner changes.