Writeback security settings

Lumel EPM allows both admin-level and user-level security for writebacks. Admin-level settings can be accessed from the Admin option in the Settings toolbar.

Navigating to Admin Portal

After navigating to the console, go to the Admin Portal.

Accessing admin portal

In the admin portal, go to Settings and look for the 'Writeback' section, which contains admin-level writeback settings.

Writeback settings

1. Writeback -> Connections Page

This page lists all writeback destinations configured by all users in your organization using Inforiver. Admin can create new connections, edit existing connections, or delete connections.

If you are working with multiple writeback connections used by multiple reports to write to multiple destinations, you can access these writeback connections effortlessly. Inforiver provides comprehensive filters and search bars to access your connections quickly.

  • The search bar narrows down the list based on the full/partial connection name that is keyed in.

  • The Connection Type filter can be used to view all the connections to a particular type of destination.

  • The Updated By filter can be used to search for connections that a particular user has updated.

Writeback connections
circle-info

Refer to this page to know more on adding and editing writeback connections.

1.1. Role-based access control for writeback admin connections

Admins can specify who can access a particular connection by clicking on the pencil icon beside it.

Edit access control for the connection

On the 'Edit Connection' page, the admin can specify the users' email IDs or an Active Directory list of who should have access to this connection.

Specify users

If a user who created the admin connection has their access revoked, they can still view the connection details in their profile's 'My Connections' tab. However, they cannot connect to it or modify its accessibility.

2. Writeback -> Settings Page

This page allows admins to enable/disable users from creating and configuring specific writeback destination types. Due to data security and confidentiality requirements, organizations would prefer users to export data to destinations created and configured by admins. This setting will allow the admin to achieve that by disabling users from creating certain destination types.

When the toggle button for a particular destination type is disabled, users will only be able to use admin-configured destinations and cannot create their own. The settings configured in the admin console will be applied to the 'Add Destination' page as well. Users will only see the destination types they have permission to add.

Destination type settings

2.1. User Access control to manage writeback destinations

Apart from choosing the allowed destination types a user can configure, admins can also limit the users who can manage writeback destinations. For example, you can let only certain users add, edit, or delete writeback destinations. Other users would be disabled from adding writeback destinations from the visual or the console.

This is done by specifying the email IDs of specific users or adding an Active Directory list in the admin console, as shown below, who will be given permission to add writeback destinations.

User access control to add writeback destinations

If access is revoked for a user who has previously added a destination, they can still view their added destination but cannot edit or delete it.

3. Permissions

The permissions option allows control over users who can writeback. It is possible to grant writeback permissions to everyone in your organization or to a select few users to perform writeback. Inforiver leverages Azure Active Directory (AAD), hence finding and granting writeback permissions to your co-workers will be straightforward.

Permissions

a) All users within specific domains

Under this option, all the users within the specified organization will be able to configure the report writeback.

b) Specific users within the domain

Selecting this option will display an input field. Users can then specify the email addresses or names of the people within the team or organization in grant writeback permissions.

Last updated

Was this helpful?