After creating a tag policy, you must bind the tag policy to specified users to take effect. There are two methods of binding.
The first method is direct filtering. Select and directly bind users. This method is suitable for scenarios where you can directly choose which tag policies to bind to a small number of sub-users, or to bind all sub-users once.
The second method is rule-based filtering. By setting certain filtering rules, sub-users who meet these rules will be selected and bound to the Tag policy. This is suitable for scenarios where tag policies are bound to sub-users in batches. For example, when there are a large number of sub-users, you must bind some first, then others.
Additionally, when filtering by rules, you must first bind sub-users to tags. For more information, see Binding or Unbinding Tags in Batches. Log in to Tag Console, go to Resource Tag, and select Cloud Access Management/User in the Resource Type to batch query sub-users and then bind tags to them.
Directions
1. Log in to the Tag Console. In the left sidebar, click Tag Policy > Policy List.
2. Select the Tag policy, and click Bind. There are 2 entries for binding. For more information, see Binding Tag Policy Entry.
3. In the binding dialog, select a sub-user, then click OK. There are 2 filtering methods for binding. For details, see Binding Filtering Methods.
Binding Tag Policy Entry
Binding in the List
1. Select a Tag policy as needed. In the operation column, click Bind.
Binding on the Details Page
1. Select a Tag policy as needed, and click Tag Policy Name to enter the details page.
2. Click Object bound to a policy. In the Object bound to a policy tab, click Bind.
Binding Filtering Method
Direct Filtering
1. On the pop-up Bind page, select Directly filter.
2. In the Select Account option:
Note:
Root account users include various types. Here all accounts include only sub-users and WeCom sub-users. Other user types will be automatically filtered. You can view the type and number of each sub-user in Cloud Access Management - User List.
Select all accounts is not checked by default, and you can directly select sub-users as required in the list.
If Select all accounts is checked. The tag policy is bound to all sub-users under the current root account.
3. Click OK to complete binding.
Rule Filtering
1. On the pop-up Bind page, select the Rule Filter method.
2. When filtering by rules, you must first bind the Tag to sub-users.
Note:
This document takes the following situations as an example:
Bind the Tag Department: Product Center A to some sub-users, assuming a total of 40.
Bind another Tag Product: Product Name 1 to other sub-users, assuming a total of 60. These 60 do not overlap with the previous 40.
For detailed operations, see Binding or Unbinding Tags in Batches. Select Cloud Access Management/User under Resource Types to search for sub-users in batches and edit their tags.
Sub-users can also bind tags for themselves. Go to Cloud Access Management - User List, click Username, and you can edit Tag on the details page.
3. Set rules respectively by choosing conditions such as OR, and AND, and then select the Tag Key and Value.
If you select OR, then choosing Department: Product Center A, Product: Product Name 1 represents taking the union. And sub-users bound with any one of the 2 tags will be selected, totaling 100.
If you select AND, then choosing Department: Product Center A, Product: Product Name 1 represents taking the intersection. And sub-users bound with both tags will be selected, totaling 0.
4. Click Preview, and then the system will filter these sub-users according to the rules.
5. After confirming, click OK to complete binding.
Viewing Historical Filtering Rules
In the filtering method, the system will automatically save the configured filtering rules, which you can view as needed.
If you select Directly filter, when all accounts are selected, it will be recorded as Directly bind all.
If you select Rule Filter when setting key-value rules, the actual conditions will be recorded. For example, Department=Product Center A OR Product=Product Name 1.
Yes
No
Was this page helpful?