Customizing Oomnitza

Customizing Oomnitza

Oomnitza allows for many degrees of customization. We've already looked into some of this when we configured Roles, set up the dashboard, and set up screens in the Mobile App. Now, we're going to look into how fields can be customized, and how to bring roles and screens together to afford complete control over asset access.


  1.  The Customization Screen
  2. Screen Builder
    1. Organizing Fields
    2. Creating Field Groups
    3. Adding Links to Field Groups
    4. Configuring field specific permissions
  3. Customize Fields
    1. Information
    2. Dropdown
    3. Display Option

The Customization Screen


All modules in Oomnitza allow customization of the fields available within the module. This allows for precise management of countless things. Instead of relying on Oomnitza to provide the appropriate fields, you can add your own to accommodate all of your most important data, and protect who has access to it.

Screen Builder

The screen builder allows you to control exactly what fields each role has access to. The screen builder is available to administrators with appropriate permissions from the view of an individual object (e.g. Asset, User, Software) in any of Oomnitza's modules. It can be accessed by opening an object and clicking the icon in the upper right:


Organizing Fields

The main function of the Screen Builder is organizing how fields are displayed for objects in Oomnitza by role. Fields can be sorted into groups, moved to an appropriate position in the detailed view, and field specific parameters can be configured to allow for even more granular permission control.

Before making changes to the Screen Builder, make sure you've selected the Role that you wish to configure the view for from the Role Dropdown in the upper right. 

From this view, you can click and drag fields to the appropriate position using the horizontal bar icon on the left. Additionally, clicking the three dots on the right will give you the ability to quickly move fields using the following actions:

Move to the top - Moves the field to the top of the current group.

Move to the bottom - Moves the field to the bottom of the current group.

Move 1 line up - Moves the field up by one line.

Move 1 line down - Moves the field down by one line.

Move field to... - Allows you to select a group to move that field to.

Creating Field Groups

Oomnitza's Screen Builder also allows you to create groups to further subdivide fields. Field groups can be added by clicking the "+Add Group" button in the upper right. 

Fields can be dragged into groups, or moved into groups based on the "Move field to..." button mentioned above.  


Groups will only appear when they have a visible field visible within them. This means that if you have relational fields or "Hide when empty" fields (see below), that will not appear on a given asset, then the entire group will be empty.

This is particularly useful in managing assets that require distinct sets of data. For example, virtual machines in AWS may have wildly different information than employee laptops. With field groups, you can isolate specific types of data.

These fields can also be expanded and collapsed when navigating the asset, making it easy to navigate through the asset and access the information you need to view.

Adding Links to Field Groups

In addition to grouping fields, you can also add a link to the top of the field grouping, which will let you navigate out of Oomnitza. This is extremely helpful when aggregating data from a variety of systems, as it can be used to provide a link directly to that Asset or other object within the external system.


To add a link, navigate to Screen Builder, and click the "Add Link" or "Edit Link" button that appears on the right of a given field group:


From here, you can specify the link URL. These URLs allow for Jinja2 templating, so you can use identifier of your existing asset to craft your link, such as "{{device_id}}.

More info on Oomnitza's Jinja2 templating can be found here.

Configuring field specific permissions

Oomnitza's Screen Builder also allows you to configure field-specific permissions that are unique to each role, and allow configuration of a role's permissions at a more granular level. When configuring a screen, click the right hand dropdown to get a list of field specific permission options.

Read-only - Makes the field read only for that specific role. This allows lower level users to view important pieces of data without being able to modify it.

Read-only and hide when empty - Makes the field read only, and hides it when empty.

Mandatory - Makes the field mandatory for that specific user.


Customize Fields

The second aspect of customization is the ability to add and edit fields in Oomnitza. Because Oomnitza can effectively track and manage anything that's uniquely identifiable in some way, it's important that you have the ability to track any element of that thing.


To add a new field, click "Add" in the upper right of the page, and you'll be presented with the following screen:


There are tabs for Information, Dropdown, and Relational Fields. Their functions are detailed below.


Name: The name under which the field appears.

Data type: What kind of data the field allows. The options are as follows:

  • Short Text - Allows the user to enter text up to 256 characters.
  • Long Text - Allows the user to enter text up to 1024 characters.
  • Numeric - Allows for entry of integers up to 20 digits.
  • Decimal - Allows for entry of decimals.
  • Date - Allows for entry of dates, gives a date box when clicked.
  • Checkbox - Allows for a checkbox or boolean field.
  • Users List - Provides a list of users.
  • Location - Provides a list of locations.
  • Custom Object Lookups - Additionally, any "Lookup" type custom objects that you've created can be created as a custom field to allow you to look up that variety of object. These fields are identified by the name of the custom object.

Editable: Determines whether or not the field is editable by the user. Uneditable fields can only be modified via the API or by a connector.

Unique: Forces data entered in the field to be unique.

Mandatory: Forces the user to enter something in the field before they're able to save or create the object.

Dropdown: Only available for short text fields. Will make the dropdown field available so you can use the newly created field as a dropdown.

Default Value: Allows you to set a default value for a field upon the creation of a new object. 


If you've selected a short text data type, and indicated that the field is a dropdown, you'll subsequently be given access to a dropdown tab.

You can use this field to create either dynamic or enforced dropdowns.

Dynamic Dropdowns are created by checking the dropdown box on the previous page, then leaving the "Enter Options" field empty on the dropdowns page. Options will be added to the dynamic dropdown as other users set new options when creating and editing objects.

Enforced Dropdowns are created by entering specific options in the field on the dropdown page. If these were entered when customizing a field, only these options will be available and required, when filling in the dropdown.

Display Option

The display option menu allows for some additional options to further customize Oomnitza.

Relational Fields

Relational Fields are a powerful tool that lets you specify that a field should appear only if another criterion has been met. For example, you could have fields that only appear for laptops, or for mobile devices, or possibly have fields that only appear at certain locations.

Relational fields can be created from any enforced dropdown field, or from fields that use Locations in Oomnitza, so you're free to create your own complex relations using custom fields.

Dynamic Dropdowns

Custom Objects also give the powerful ability to create Dynamic Dropdown fields that provide different choices depending on the value set in another field.


If you've been going through Oomnitza's getting started guide, then you're probably beginning to notice that everything is coming together. You've learned how to use the general functions, and how to tune them for your organization. There are many advanced things Oomnitza can do, but for now, all  that's left is setting up your Oomnitza Integrations —>



Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk