Contents x
    Zendesk - Assign Group to Users
    • 29 Aug 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Zendesk - Assign Group to Users

    • Updated on 29 Aug 2024
    • 3 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Zendesk - Assign Group to Users assigns a group to a Zendesk user for each user returned by the saved query supplied as a trigger (or devices selected in the asset table).

    See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

    General Settings

    • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
    • Add description - Add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
    • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
    • Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
    • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

    • Use stored credentials from Zendesk adapter - Select this option to use Zendesk connected adapter credentials.
      • When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
    Note:

    To use this option, you must successfully configure an Zendesk adapter connection.

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Group IDs (comma separated) - Enter a comma separated list of group IDs. Users will be added to or removed from these groups.
    • Add assignment - 'Add' is selected.

    • Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

    Additional Fields

    These fields are optional.

    Connection Parameters

    If Use stored credentials from the Zendesk Adapter is disabled, these fields are required:

    • Sub Domain (required) - The subdomain used to access Zendesk. For example, Axonius is the subdomain for https://axonius.zendesk.com/.

    • User Name (required) - The username of an Axonius dedicated user account.

    • API Key/Token (required) - An API Key/Token associated with a user account that has permissions to fetch assets.

    • Password - The password of the Axonius dedicated user account.

    • 2FA Secret Key - The secret generated in Zendesk for setting up two-factor authentication for the Zendesk user created to collect SaaS Management data. See Zendesk documentation for instructions on how to set up two-factor authentication (2FA) and generate the 2FA secret.

    • Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

    • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

    • HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

    • HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

    • Justification reason (optional) - The reason for assigning the group to the user.

    • Gateway Name - Select the gateway through which to connect to perform the action.

    APIs

    Axonius uses the Zendesk Update User API.

    Required Permissions

    This action can be performed by Zendesk Admins and agents in custom roles with permission to manage end users or team members.
    Agents can only update end users. Administrators can update end users, agents, and administrators.

    For more details about other Enforcement Actions available, see Action Library.

    Was this article helpful?
    What's Next