Skip to main content

71 docs tagged with "Configuration"

View all tags

Activity forms

The Activity form is the form the user sees when running a process. It is used in every step of the process for explaining what the activity is for and for entering/submitting the information which is relevant for that activity.

Adding owner to onboarded systems

The Onboarded systems view contains the necessary configurations to manage an external source system from which you want to import data from, and for access systems, provision data to.

Application Insights

Application Insights (AI) is an extensible Application Performance Management (APM) service that allows for the monitoring of applications running both on-prem and in Azure.

Avoiding unintentionally deleted contexts

In a standard installation of Omada Identity, contexts are deleted when they are no longer delivered from an HR system. If you or your organization delete contexts unintentionally, the result may be that unintentional deprovisioning takes place. To avoid this from happening, you can enable this feature by configuring Omada Identity Data Warehouse, Omada Identity RoPE, and Omada Identity.

Business contexts

Omada Identity has a business context concept that allows you to manage one or more types of business contexts, for example, the organizational structure, or a project hierarchy.

Context assignments

The relationship between an identity and a context is called a context assignment. An identity has a context assignment to a context - either a direct context assignment or a membership-based context assignment.

Control elements

A control element is a process design element that controls the progress of a process, and which is not an activity.

Control policy

See how to configure control policies in Omada Identity Cloud

Customer settings

Some customer settings only become effective with the start of the next import.

Data object exchange web service

Omada Identity features a data object exchange web service. You can use this service to test and automate an Omada Identity implementation. The main purpose of the web service is to integrate with and automate smaller datasets.

Data objects

Learn about the Omada Identity Management data objects

Data sources

You can use a new Data Source data object type to represent SQL data sources. To access data sources, go to Setup > Administration > Connectivity... > Data sources.

Delegation of self-management roles

Using the Delegation process, it is possible for an Owner/Manager to delegate the self-management role to another user. This can be used for example when a user is on holiday and need to temporarily delegate access rights to a colleague.

Direct Resource Assignments

There are several processes and features that will create a Resource assignment object for a self-management resource.

Email notifications

This page contains third-party references. We strive for our content to always be up-to-date, however, the content referring to external vendors may change independently of Omada. If you spot any inconsistency, please report it to our Helpdesk.

Email templates

Email templates are used in Send email actions, enabling you to send email notifications whenever a defined process event occurs.

Engine configuration

Some basic configurations are set in the in EngineConfiguration.Config file located in C

Event actions

An event action is an action which will take place when an event happens. Omada Identity includes the following event actions:

Event definitions

Event definitions allow you to automate actions based on timers, survey steps, or the creation or the update of an object.

Event Logging configuration

This page contains third-party references. We strive for our content to always be up-to-date, however, the content referring to external vendors may change independently of Omada. If you spot any inconsistency, please report it to our Helpdesk.

Gmail service account SMTP OAuth to send emails

This page contains third-party references. We strive for our content to always be up-to-date, however, the content referring to external vendors may change independently of Omada. If you spot any inconsistency, please report it to our Helpdesk.

Manual owners

You can manage owners directly in Omada Identity Cloud by using an option called Manual owners. This allows you to update a property in the Portal via a form, event, or process to manually assign and maintain owners.

ODW integration

The ODW Integration package creates menu items for the standard ODW SSRS reports, and data object types and properties used for the ODW Export.

On-premises configuration

In this section, you can find information on on-premises specific configuration. Click on each tile to learn more.

Ownership

Learn how to assign ownerships of objects in Omada Identity. These objects can be Identities, Contexts, Resources, and other objects.

Ownership and self-management

To manage access to Omada Identity, including ownership of objects and memberships to user groups, ownership, the Management concept requires that you enable the Self-management extension in the Role and Policy Engine (RoPE).

Process designer

The Process designer allows you to draw up your business process in a visual editor and modify and configure it as you go along.

Process templates

A Process template defines the activities, steps, and procedures that must be carried out to complete a defined business process.

Reference paths

A central concept of Omada Identity is the data object model. This feature allows you to build arbitrary data object types and assign a number of properties to them. You can use such properties to, for example, add text or a number, but you can also use properties to create references to other data objects. This type of property is known as a reference property.

Registry settings

There are several settings related to Enterprise Server that you can change in Microsoft Windows’ Registry. These settings control some overall settings that are very important for Enterprise Server. They are all of the type REG_SZ.

RoPE-related customer settings in Enterprise Server

Some settings for RoPE are set in Enterprise Server and they are described in the table that follows. You can change the settings in the Omada Identity Portal in Setup -> Administration -> More… -> Customer settings.

Sequences

The Sequences view allows you to customize the order numbers of the data objects created.

Set up a reference path on a view

The following procedure is an example of how you can set up a reference path on a view. In this example, the aim is to create a view with resource data and to display a column with the owner of the system to which a resource belongs.

Shadow data objects

A shadow data object is used to drive the execution of event definitions for object types other than actual data objects.

Specifying reference path

A reference path consists of a number of fragments that are separated by a forward slash or backward slash.

System settings

Omada Identity enables you to set a number of system settings in various locations that all relate to how you want your system to look, feel and respond to users of the system.

Timer Service

The Omada Identity Timer Service is responsible for running timers and for firing the timer events.

Transfer ownership survey

The Transfer ownership survey is used to transfer ownerships of objects when an identity is leaving the organization.

Transitions

A transition is a link from one activity or control element in a process to the next. A transition defines the passing of control from one completed activity to another.

Translations

Translated application strings are stored in the translation XML files located in the \bin folder (by default, C:\Program Files\Omada Identity Suite\Enterprise Server\website\bin). The files have an .xml extension, for example, en-us.master.xml is for American English, and de-de.master.xml is for German.

Tree structure

In Omada Identity, all data objects are located in the same global tree structure. The tree structure allows you to see at a glance how objects are connected, and their permissions relative to users and user groups. You can access the Tree structure dialog box under Setup > Administration > More...

Using email templates with event definitions

To use an email template, you need to create an event definition and connect an email template with it. Events that trigger an email notification to be sent out can be, for example, approval or rejection of an access request or removal of an assignment due to an access review.

Web.config configuration settings

The Web.config file allows you to configure several of the Enterprise Server settings that can either be set in the config file or in the Windows Registry.

Work weeks

Omada Identity allows you to configure and specify work weeks. You can use this feature for calculating durations based on your organization's work weeks, or to trigger timers inside specific time slots.