--- title: "Register Custom Security Definitions" slug: "register-custom-security-definitions" updated: 2024-03-29T07:15:31Z published: 2024-03-29T07:15:31Z canonical: "skthelp.syniti.com/register-custom-security-definitions" --- > ## Documentation Index > Fetch the complete documentation index at: https://skthelp.syniti.com/llms.txt > Use this file to discover all available pages before exploring further. # Register Custom Security Definitions > [!NOTE] > Note > > This section only applies to custom components. Use a security definition to assign a key to limit a user's access to content. > [!NOTE] > Note > > Security definitions are assigned to roles. When a user is assigned to a role, the key value(s) assigned to the role's security definition(s) restrict the user's access to that content only. Security definitions are assigned to roles and restrict access. Refer to [Assign Keys to Security Roles](/v1/docs/assign-keys-to-security-role) for more information. To view the security definitions assigned to a page, select **Admin > Security Management > Security Pages** in the *Navigation* pane, and click the **Security Definitions** icon. This topic contains the following sections: - [Add a Custom Security Definition and Key](/v1/docs/register-custom-security-definitions#add-a-custom-security-definition-and-key) ## Add a Custom Security Definition and Key To register custom security definition for a custom WebApp in System Administration: 1. Select **Security > Security Management > Security Definitions** in *Navigation* pane. 2. Click **Add**. [View the field descriptions for the Security Definitions page](/v1/docs/create-security-definitions) 3. Enter a unique name of the definition in **SECURITY DEFINITION NAME** field. 4. Select a data source where the view for the security definition is stored from **DATA SOURCE ID** list box. 5. Select the view created in the [Create a View](/v1/docs/create-a-view) section from **DATA VIEW** list box. > [!NOTE] > Note > > Only views that reside in the DATA SOURCE ID are available in the DATA VIEW list box. This view must reside in the selected data source and must be named as web*Sec. The columns in this view are used to restrict user access on pages where the security definition is applied. The view can also contain a column named “FriendlyName” that is used as a display value by on-site administrators when selecting specific key values. 6. Enter a brief description or explanation of the security definition in **DESCRIPTION** field. 7. Click **Save**. 8. Click **Keys** button to define key columns within the DATA VIEW that contain values by which security can be administered. > [!NOTE] > Note > > If defining multiple keys, additions, deletions and updates to keys must be done during a single editing session. 9. Click **Add**. [View the field descriptions for the Security Definitions Keys page](/v1/docs/security-definition-example) 10. Select a column within the view from **COLUMN NAME** list box that contains values by which security can be administered. 11. Click **Save**. The key value used by the security definition is set at the security role level on the [*Security Role Key Values*](/v1/docs/security-role-key-values) page. Refer to [Add Keys to a Security Role](/v1/docs/assign-keys-to-security-role) for more information.