Skip to main content

Editing a user access rule

A user access rule defines which users that have access to the available tokens. You can edit existing rules.

Do the following:

  1. Select License management on the QMC start page or from the StartS drop-down menu to display the overview.

  2. Select User access rules in the panel to the right.
  3. Select the rule you want to edit.

  4. Click Edit in the action bar.
  5. Edit the properties.

    Operator Descriptions and examples
    =

    This operator is not case sensitive and returns True if the compared expressions are exactly equal.

    Example:  

    user.name = ”a*”

    The user named exactly a* is targeted by the rule.

    like

    This operator is not case sensitive and returns True if the compared expressions are equal.

    Example:  

    user.name like ”a*”

    All users with names beginning with an a are targeted by the rule..

    !=

    This operator is not case sensitive and returns True if the values in the compared expressions are not equal.

    Example:  

    user.name != resource.name

    All resources that do not have the same name as the user are targeted by the rule.

    When using multiple conditions, you can group two conditions by clicking Group. After the conditions have been grouped, you have the option Ungroup. Additional subgrouping options are Split and Join. The default operator between conditions is OR. You can change this in the operator drop-down list. Multiple conditions are grouped so that AND is superior to OR.
  6. Click Apply to save the updates.

    Successfully added is displayed at the bottom of the page.

Information noteIf a user access rule is deleted, and there are currently users with tokens allocated due to this rule, these tokens will not automatically be released. They have to be released manually.

The users named in the rule have access to the application as long as access tokens are available.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!