About Responsibilities

Responsibilities provide access to specific Views to particular users. Different types of users need access to different views for varying functional reasons. For example, a sales representative should not be working on service requests and a field service engineer should not be creating marketing campaigns for visibility reasons or a partner user should not be able to see sales opportunities that partners from a different company are working for competitive reasons.

In addition to security and functional reasons, Responsibilities ensure that users are able to focus on the information most relevant to them. Responsibilities allow you to present only those views that a user actually needs to do their job by providing a many-to-many relationship between Views and Users.

The easiest way to conceptualize and define Responsibilities is to consider generic job classes. For example, sales representative, sales manager, service technician, or even CEO. These are classes of job that require access to different types of data. For example, sales users need access to sales-related data, such as sales opportunities, while service users need access to service-related data, such as service requests and require access to different levels of data and sales representatives need access to the data of customers that they directly work with, while service users need access to service data for all customers.