My ideas

Security rights in Jedox are always handled on an object basis. I.e., a Jedox admin always has to navigate to the object itself (database, report file/folder, ETL project, or group dimension right cubes etc) and then set rights accordingly. While ...

Currently every group of the user that is creating a new database (= database in modeler and also every new rgrp or fgrp) will get a D right for the newly created database. For security reasons every user on our platform is asigned to an azure gro...

Recently, we introduced a password policy for users. On the platform itself nowhere is explained how the policy should look like. Users need to google or check in KB for that information. It could be a small display below or icon "i" where on the ...

It is desired that after a new user has been created by the admin with a default password, the corresponding user is forced to enter a new password. Gladly with the desired password complexity from https://feedback.jedox.com/ideas/JS-I-462

Whilst you need to ensure that there is always at least 1 account that is a member of the Admin role (via a group), it does not need to be the default Admin user account that is shipped with the product. The issue is that this is a basic authentic...

In the current implementation workflow (including the protection of changing cell values and executing procedures) is implemented in designed web reports. Users using views, the Excel add-in or other methods to access database cells can bypass the...

When adapting or extending a Jedox environment you often need to create new users/user groups/roles that are only slightly different from the ones that are already existing. Right now you need to create those users/roles/user groups from sratch an...

It would be useful to have additional options for filtering Journal entries, specifically the following categories: "Balance Constraint" "Created By" "Modified" "Modified By" "Posted By" "Legal Entity" All of these labels are shown in the "Posting...

Extend the storage to capture reporting positions for the notes (text narratives and tabular information) which cannot be captured by the existing cubes. Provide sample data and reports for the most common notes sections.

Users would benefit from an easy way to set up custom data validations, similar to the setup of consolidation rules. E.g. the amount on a PnL Account needs to match a movement on a BS Account.