---
sourceDocument: Yokohama Data and Automation
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/integrate-applications

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Data and Automation

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Infoblox roles and permissions

# Infoblox roles and permissions {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Define the roles and permissions that the Infoblox activities need to access the
various resources on the Infoblox server.

## Admin groups

There are three types of admin groups on an Infoblox server:

* Superuser
* Default
* Limited Access
{#infoblox-roles-permissions__ul_sgz_sl2_gw}

To perform specific operations on the Infoblox server, the Limited Access user must have a
minimum set of privileges for the desired resources, using either the user interface or an
API. These privileges are based on read and read/write access. For more information, refer
to the "About Admin Groups" section in the Infoblox NIOS Administrator Guide.

## Permission hierarchy

1. User: A user can be part of multiple groups.
2. Group: A group can have many roles.
3. Role: Each role consistes of specific resource permissions.
{#infoblox-roles-permissions__ol_yly_tm2_gw}

## Required permissions

The ServiceNow Infoblox activity pack requires appropriate read and read/write privileges for these resources:

* Network
* DHCP
* DNS
* IPAM
{#infoblox-roles-permissions__ul_rhw_qml_gw}

This example shows a default DHCP admin role, its resources, and the related permissions
for each.  
Figure 1. Infoblox permissions