You can change the name and description of a taxonomy. If you plan to apply the top node of a taxonomy as a category, you may want to change the category parameters. For more information, see Editing a Category.
To edit the name and description of a taxonomy using the Web Portal
To edit the name and description of a taxonomy using PowerShell
If a taxonomy has been in use, you should use extreme care deleting it. When you delete a taxonomy:
If you choose to delete a taxonomy, you should ensure that the proper administrators are notified so that policies, attestations and reports can be modified as needed. A safer approach may be to delete categories individually. For more information, see Deleting a Category.
To delete a taxonomy using the Web Portal
To delete a taxonomy using PowerShell
The proper configuration of a category is integral to a properly working system. Categories should be created and refined in test mode, and published when they are ready to be used in your production environment. Deployments of categories should be properly managed. See Managing the Life Cycle of Taxonomies and Categories for more information.
You can work with categories using the following methods:
Each category has a number of settings, which have an impact on the category’s behavior. In the table below, the parameter in brackets is the PowerShell and XML equivalent of the setting in the Web Portal.
Setting | |
Category Risk (Risk) |
Indicates the relative risk of the category. This is then used to determine how a resource is classified. For more information, see Classifying Resources. |
Publish this category (IsPublished) |
Makes a category available for manual categorization. You must also enable this for automation to work. Publish a category only when you are ready for business owners to have access to it. A subcategory must have a published parent category. If you publish a subcategory, and the parent is unpublished, the action is ignored. |
Allow this category to be used by the automated system (IsAutomaticClassificationEnabled) |
You can make a category available to the automated system. Automated categorization is based on the rules associated with the category, so you should associate rules and test the category before automating it. Automation will not take place until the category is published as well. |
Govern using this category (CausesGovernance) |
When a category that causes governance is applied to a resource, that resource is placed under governance and can be managed using the Web Portal. Resources under governance can be subject to polices and attestations. |
Mutually Exclusive (IsMutuallyExclusive) |
The mutually exclusive setting applies to the children of a category. If a category has been defined as mutually exclusive, only a single subcategory can be applied to a resource. For example, consider a category in your taxonomy called PHI, which has three subcategories: Level 1, Level 2, Level 3. If PHI is set to mutually exclusive, you can only apply one of the subcategories. To create an entire taxonomy that is mutually exclusive, so that only one category can be assigned from the taxonomy, all parent categories must be set to mutually exclusive. When more than one category could be applied to resource based on the associated rules and category threshold, the category with the highest combined rule score is applied. |
Strictly Ordered (IsStrictlyOrdered) |
Strictly ordered is a special kind of mutual exclusivity, in which the order of the subcategories has meaning. When more than one category could be applied to a resource based on the associated rules and category threshold, the category closest to the parent category will be applied. For example, if your categories are Level 1 and Level 2, in that order, and either category could be applied, in this case Level 1 will be applied. If you are planning on creating a strictly ordered category, ensure you enter the subcategories in the correct order. There is no way to change the order of subcategories once they are created. You must delete and recreate the categories, including assigning the rules. |
Threshold | The threshold value determines whether a category is applied. Combined with the weights given to a rule when you associate it, and the match strength of the rule, the threshold gives you control over what causes a resource to have a category applied. For a full explanation, see How Rules Affect Categorization. The default threshold is one. Note: The threshold can only be modified through PowerShell commands. |
The first step is to create the category, giving it a name and description. A category requires a parent, which can either be the top level taxonomy node or any category in the taxonomy. By default, new categories:
You should not change these values without fully understanding the implications for your classification system. For more information, see Working with Categories. |
Each category can only belong to a single taxonomy. If you have created a category in one taxonomy and want to move it to another, see Moving a Category.
To create a category using the Web Portal
To create a category using PowerShell
© 2025 One Identity LLC. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center