So far, we have seen how to build and secure a Force.com application. In this chapter, we will take a look at ways to administer the application and the available tools that will help us achieve these.
We will cover the following topics in this chapter:
- Managing the access control
- An overview of Force.com licenses
- Restricting data access
- Understanding the stakeholders in the organization
- Understanding the security pyramid
- Managing profiles
- Setting up roles
- Sharing settings
- Managing different types of accounts
Now that we know how to build an application on Force.com, it is time to set up the platform to be used. We are going to bring everything we learned so far and put them together to be used by different people. So, let's begin.
Any enterprise application is built for multiple users at different levels. Different types of users will require different types of access controls. Different departments will use different applications as their daily drivers. For example, the support call center users need the service cloud but have limited or no access to Leads and opportunities. Similarly, the cold calling team may not be able to see the cases and solutions but will be able to see only the leads. The application should simplify their job and not add complications to it.
In the Library Management System, the librarian has complete access to the entire library database, but the clerks who are dealing with check-in and checkout transactions do not need to access the books table to modify it. There will also be a few administrators and superusers who will customize the application based on their requirements.