# View Profiles

If you work with multiple roles and users, you will most likely need to customize the display of the 4ALLPORTAL for some roles. You may want to assign e.g., an extended/object-type specific metadata renderer for role "Photographer", assign a specific layout to remove a subpanel, or add a button. To accomplish this, you can assign a view profile to one (or multiple) roles.

A view profile contains an object renderer and layout mapping. You can select one or multiple modules and assign specific object renderer sets and layout sets which will apply for those modules only.
If no view profile is assigned to a role, or if a module is not set in any of the assigned view profiles, users will see the default object renderers and layouts.

View profiles are only optional. The only exceptions are Shares (more details).

Please note: Creating a view profile is only one step for a role-specific display of a module. All steps are:

consider what you actually need for what user role
create and store your custom object renderer (and layout) with the required changes from the default in your file system
create the required object renderer sets (and layout sets) in admin snap-in Module configuration/{module}/Object Renderer Set (and Module configuration/{module}/Layout Set)
compile the mapping for the required modules as a view profile (step-by-step guide)
assign the view profile to a role in admin snap-in General system configurations/User settings/Role configuration

Where the creation object renderer sets and layout sets is module specific, view profiles work across modules.

Further Documentation

# Create a View Profile

View profiles are created and configured in admin snap-in General system configurations/User settings/View Profiles. To create a new view profile, click toolbox action "Create":

To configure, you need to make the following settings:

Enter a unique name and a description (e.g. "Picture desk" and "Renderer and layout settings for picture desk staff")
Renderers:
- Choose the module for which you need a renderer other than the default (e.g. "Files").
- Select the object renderer set with the specific renderers you need instead (e.g. "Picturedesk").
  Please note: Only object renderer sets defined for the selected module are shown in the dropdown.
- Click the + button for further modules, if required.
Layouts:
- Choose the module for which you need a layout other than the default (e.g. "Collections").
- Select the layout set with the specific layout you need instead (e.g. "collection_reduced"). Please note: Only layout sets defined for the selected module are shown in the dropdown.
- Click the + button for further modules, if required.
Assign all roles that need this profile in panel "Roles". This can also be done in the role configurations (more details).
Save your settings. The new profile is now available in your role configurations, panel "View Profiles".

Note that a view profile does not have to be complete with all modules to work. It only contains the differences from the default.

Storage in the File System

View Profiles are stored globally in your custom folder, path global/view_profile.

# Assign a View Profile

To assign a view profile to a role, go to admin snap-in General system configurations/User settings/Role configurations. Select a role from the tree structure and open panel "View Profiles" (tab "General/User"):

To assign a profile, click the "link" icon and select a view profile from the opening pop-up window. In this pop-up, all view profiles created so far will be listed. Save your settings and reload the system.

# Assign Multiple View Profiles

If required, a role can be assigned more than one view profile. For example, role "Photographer" needs the specific metadata renderers from view profile "Photographer" as well as layout settings from view profile "Externals".

# Order and Ranks

If a role has assigned more than one view profile, the profiles will not merge or overwrite each other. For a module, only one view profile can apply. There are two options:

Example 1: Two view profiles with all different modules
If a role has assigned one view profile for modules A and B, and one view profile for modules C and D, all renderers/layouts will apply as soon as they are requested in modules A, B, C, D.
Example 2: Two view profiles with overlapping modules
If a role has assigned one view profile for modules A and B, and one view profiles for modules B and C, the renderer/layout set with the higher rank will apply for module B.

# Rank

If two (or more) view profiles include an object renderer/layout set mapping for the same module, the view profile containing the object renderer/layout set with the higher rank wins and applies (the higher the number, the higher the rank). A set with rank 10 would win over a set with rank 5.
The rank can be defined in the corresponding module's object renderer/layout set:

Please note: A whole object renderer set or layout set will win for a module. From the set with the lower rank, all renderers/layouts will not apply (compare Example 2).

Further Documentation

# Shares

For shares, there is always a virtual role. This role will not display in the role configurations, so you cannot assign a view profile there. If you want your share users to get a specific layout, you need to:

map that layout in a layout set of the corresponding module
add this layout set to a view profile
add this view profile to your share configuration (using either field View profile in admin snap-in Module configurations/{module}/Shares, or tag <view_profile> in the share configuration xml)

As a comparison, you can have a look at our default share "eTicket".

Default share eTicket

For default share "eTicket" from module Files, the system comes with:

default view profile "share_eticket"
default layout set "share_eticket"
default layouts "main/share_eticket" and "detail/share_eticket"

This view profile is added to configuration file eticket.xml like this: <view_profile>share_eticket</view_profile>.

# Examples Use Cases

# Example 1

Your HR department requires an additional subpanel in the Users module to manage employee contract information. You need one view profile:

Your view profile "HR" maps a corresponding layout set which extends the default layout for the User module.
You can assign this view profile to role "Human Resources" and only this role will see the subpanel.

# Example 2

You want your freelancers to see only a reduced view of the DAM. Only your photographers require a specific, detailed import_tagging renderer for the Files module. You need two view profiles:

Your view profile "Freelancer" maps:
- an object renderer set which reduces the default metadata renderers of the Files module. Its rank is 2.
- an object renderer set which reduces the default metadata renderers of the Collections module. You can assign this profile to your three freelancer roles "Photographer", "Copywriter," and "Editor".
Your view profile "Photographer" maps
- an object renderer set which reduces most default metadata renderers of the Files module, but extends the default metadata renderer "import_tagging". Its rank is 10.
  You can assign it to role "Photographer" additionally to view profile "Freelancer".

Because the module Files is part of both view profiles, the rank of the set decides and for module Files, the view profile with the higher ranked object renderer set applies.
As an effect, photographers will get a reduced freelancer view for module Collections, but the extended import_tagging renderer for module Files.

Please note: Remember that the lower ranked set will not apply for that module with all its renderer/layout mappings . If you require specific renderers/layouts from the lower ranked set, you need to configure it for the higher ranked set also.

← Tracing with Jaeger Allow Duplicated Files In Collection →