Data

The data classification part of the platform governs the relations between users and how data can be accessed.

Attributes

In order to provide teams with a tailor-made environment to cater users' needs and an efficient method of managing them, we provide attribute customization and grouping. You can read more about what an attribute is in our Terminology.

Attributes list

All user attributes used in the Users section come from the Attributes menu item, where they can be edited or moved up / down in position, as they will be displayed on the user's profile.

For example, in the case of the user below, we will notice that the attributes of firstname, lastname, birthdate and gender, belonging to the Attribute category of Personal information are occupying the first 4 positions. The following attribute category is Employment information, with its 2 attributes and so on.

Attributes have default names which you can customize in the default language. In addition to this, you can also assign the attribute to an attribute category, specify the data type, if it is in use, make it required, visible or default.

Attribute categories

Attribute categories are groups of attributes used for a better attribute classification. You can add new attribute categories and edit the existing ones' information and position to fit your needs.

When creating a new attribute category, you need to fill in the following information:

• Category code. You can assign a code to a category to help you find it faster.
• Category name. Give categories custom display names, which will appear in users' profiles.
• Category description. Add a short description to that category to help customer care representatives better understand what it is about.

Once you've filled in the required information, you need to assign the new attribute category to a collection and make it visible or not.

Accessing attributes

A user is only able to access the Attribute configuration menu item within the platform if that user has at least one Admin role that grants him that permission.

Events

You can customize how and what information should be displayed in the Dashboard and Reports sections of the platform.

Events list

As described in our Terminology page, events are actions or occurrences that are handled by Delegated User Management.

A full report of the events is available within the Reports section, but in order for them to be displayed there, they must be set up in the Data menu first.

Events come with default values for their names, but you can customize them by editing the event.

When editing the event, you can do the following customizations:

• Change the event display name. You can give a custom name to that event for easier reporting and filtering.
• Assign the event to an event category. Organize events by assigning them to existing categories.
• Enable event processing. If processing is not enabled for an event, it will not be displayed within your Dashboard & Reports.

Event categories

Events can be grouped into custom categories, allowing you to access and filter them easier. The Event categories tab helps you view, define and edit the event categories where your events will fall into, or simply search and filter them.

You can edit and delete existing event categories, but keep in mind that once you assign events to a category, you cannot delete that category until you have moved all its events to another one.

To create an event category, click on the + Add event category button and fill in the event category's information:

• Category code. Assign a code to that category to help you find it faster.
• Category name. Give the category a name of your choice.
• Category description. Briefly describe that event category to make life easier for other users.

Additionally, you can specify if the events in that category are related to consent and also activate/deactivate it.

Accessing events

A user is only able to access the Event configuration menu item within the platform if that user has at least one Admin role that grants him that permission.

Structures

A structure represents a logical means of organizing users.

There are two main types of structures within the platform:

Static structures

These are groups that the organization defined manually. Furthermore, users will have to be associated to the groups defined under these types of structures by an organization user (employee, partner, etc.) with the proper access rights. The system provides ways to automate this step through different sets of rules and mass updates.

Dynamic structures

These are groups that are inferred from the attributes that are already associated to an identity. Furthermore, those respective users are automatically added to the structure groups based on their attribute values. For example, grouping users by country and city can be done by defining a dynamic structure (as long as the identity has these attributes associated).

Regardless of the structure type, it can be defined on a single level (flat structures):

or can be nested on several levels (nested structures):

Note that any identity can be part of one or more structures at any given point.

Structures are the main instruments that will allow granular control over what users and the associated data a specific role can control.

Accessing structures

A user is only able to access the Structures configuration menu item within the platform and to create new structures if that user has at least one Admin role that grants him that permission.

Furthermore, considering that the user was granted access to the Structures menu item, he is only able to manage the structures created by him and the ones that he has entitlements over.

Adding a structure

All structures are defined per segment, receive a code and are of a particular type (static, dynamic, flat or nested). These fields cannot be edited once a structure is defined. In order to save a new structure, these need to be assigned a:

• A name;
• In case of static structure, at least one group (or structure item);
• In case of dynamic structures, at least one attribute that will be used for creating the structure groups.

In case of dynamic structure, there are multiple options available for generating the structure:

• From one or multiple user attributes;
• In a flat or nested way
• Based on a complex attribute, which would lead to the automatic creation of groups based on the sub-attributes of that complex attribute.

For example, you might have a country - region nested structure represented under one attribute (e.g. location) with multiple groups associated to a user as: {Germany > Berlin | United Kingdom > London}.

Editing a structure

Except for the field mentioned above, the rest of the fields can be edited under the following conditions:

• in case of static structures, new groups can be added or the name of a group can be edited. However, deleting a group is only possible once all users belonging to that group have been moved to another one, hence only for empty groups. Also, in case the group was used in a rule, users' roles will need to be updated. Note that these updates run periodically as system jobs so the changes at the user level will not happen automatically.
• in case of dynamic structures, as they save the pattern for generating the structure out of users' attributes, these can be updated at any time without affecting users' associated groups. However, if there are rules based on these structures, they will be updated periodically through the system job responsible for that.

Deactivating a structure

Deactivating a structure will not affect current users and their relations with it, but will make the structure unavailable for future use (e.g. association to other users).

Deleting a structure

Deleting a structure is irreversible and is only possible if there are no users within that structure.