Customizing Screens in Oomnitza

Oomnitza's screen builder is a powerful tool that allows Oomnitza administrators to precisely configure how different users are able to view objects.

Note: Screens are configured on a per role basis. When configuring screens in Oomnitza, make sure you've selected the desired role before making configurations in the screen builder.

Accessing the Screen Builder

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.


Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk