{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":6670,"path":"customer-service-management/declarative-resposibility-framework.md","title":"Configure access through the responsibility access configuration","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure access through the responsibility access configuration\n\nStreamline how you create and update your responsibility definitions and access configurations by using the declarative responsibility framework in the Customer Service Management \\(CSM\\) application. This framework enables you to select the level of access for each responsibility by leveraging low-code or no-code capabilities, which reduces the time required for scripting.\n\n## Before you begin\n\nRole required: One of the following roles:\n\n-   sn\\_crm\\_customer\\_access\\_management\\_admin\n-   sn\\_crm\\_foundation\\_admin\n-   admin\n\n## About this task\n\nThe Responsibility Access Configuration \\[sn\\_customerservice\\_responsibility\\_access\\_config\\] table is used to store the metadata of the responsibility access configuration. With this configuration, you can enable different levels of access for related party users across different records of the same entity. For example, a user with a location manager role might serve as a fulfiller at one business location and as an agent at another.\n\nFor more information about creating a responsibility definition, see [Create a responsibility definition](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/t_CreateAResponsibilityDefinition.md). The need for domain separation in configuring access records is determined by the domain of the referenced responsibility.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Customer Service** &gt; **Administration** &gt; **Responsibility Definitions**.\n\n2.  Select a responsibility definition record.\n\n3.  From the Responsibility Access Configuration related list, select **New**.\n\n4.  On the form, fill in the fields.\n\n<table id=\"table_xqp_24b_1yb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nResponsibility\n\n</td><td>\n\nResponsibility applicable to this configuration, for example, account manager or authorized representative.\n\n</td></tr><tr><td>\n\nActive\n\n</td><td>\n\nStatus of the configuration. By using this functionality, you can enable or disable a responsibility access configuration.The default value is **True**.\n\n</td></tr><tr><td>\n\nRoles required\n\n</td><td>\n\nRoles required in addition to responsibilities to get the access.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nProvides a description of the purpose or function of the responsibility access configuration.\n\n</td></tr><tr><td>\n\nAccess levels\n\n</td><td>\n\nLevels of access for the accessible entities. The list shows the access levels, including read, write, and full. **Note:** Full represents a special access level that is equivalent to read, write, and create.\n\n</td></tr><tr><td>\n\nAccessible table\n\n</td><td>\n\nEntities or records accessible through this configuration, like cases or sold products.\n\n</td></tr><tr><td>\n\nAccessible table filter\n\n</td><td>\n\nAdditional conditions to filter the accessible table.\n\n</td></tr><tr><td>\n\nRelationship table\n\n</td><td>\n\nRelationship table where this configuration is applied, for example account team member \\[sn\\_customerservice\\_team\\_member\\] table.\n\n</td></tr><tr><td>\n\nRelationship filter\n\n</td><td>\n\nAdditional conditions to filter the relationship record applicable to the user.\n\n</td></tr><tr><td>\n\nType\n\n</td><td>\n\nType of association between the accessible and relationship table. Listed are three types of association:\n\n-   Simple\n-   Dependent\n-   Advanced\n\n\n</td></tr><tr><td>\n\nRelationship field\n\n</td><td>\n\nField on the relationship table to be used for association.\n\n</td></tr><tr><td>\n\nAccessible table field\n\n</td><td>\n\nField on the accessible table to be used for association.\n\n</td></tr><tr><td>\n\nDependent table\n\n</td><td>\n\nTable that contains the mapping between the relationship field and accessible table field.\n\n</td></tr><tr><td>\n\nDependent relationship field\n\n</td><td>\n\nField on the dependent table that maps to the selected relationship field.\n\n</td></tr><tr><td>\n\nDependent accessible table field\n\n</td><td>\n\nField on the dependent table that maps to the selected accessible table field.\n\n</td></tr><tr><td>\n\nField values script\n\n</td><td>\n\nScript that returns the valid association values for advanced association logic.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nProvides a description of the purpose or function of the responsibility definition.\n\n</td></tr></tbody>\n</table>    **Note:** To create entries to the **Applies to Relationship**, **Access Levels**, or **Accessible Entities** fields in the Responsibility Access Configuration table, you must migrate all existing configurations for these fields in the global.CSMRelationshipConstantsSNC script include.\n\n5.  Select **Submit**.\n\n\n"}}