What's New

Every 2 weeks we update our Authorization Box with new features and bug fixes. On this page you have an overview of all updates based on our release notes.

All release notes are grouped below.

The Authorization Box was updated on March 13, 2023. Below You will find the most important changes:

Show to which Organization Roles a Template is assigned
On the edit page for an Authorization Template we added an overview that shows to which Organization Roles a Template has been assigned.

Block an Organization Role
We added the functionality to block an Organization Role. A blocked Organization Role can no longer be assigned to a user.

You can only block an Organization Role when there are no outstanding request that concern that role.

Blocking an Organization Role has no further consequences for a role. The role can still be revoked in an Authorization Request and users that have the Organization Role assigned to them, can still keep using the permissions that are are linked to the Organization Role. Altering the role is also still allowed.

Mention database connection in notification messages
We added the database connection in the header of the notification messages, so that You know to which connection the notification applies.

Display Authorization Requests in the order they are processed
A new column “Processed on” is added to the overviews of processed Authorization Requests, so that the requests are displayed in the order they are processed and no longer in the order they are created.

• Free field of type Date is written to Business Central in a wrong date format.
• Not all Analysis Results for Conflicting Permissions have a value in the Type column.
• Processes and Categories are only linked to a NAV/BC monitoring license and not to an AX/F&O monitoring license.
• Filter Review for Analysis Results Critical Permissions doesn't work (AX/F&O).
• The field “Email for warnings” is obligatory for all authentication methods, while it only concerns OAuth connections.
• From the Critical Permission page, when you review Conflicting Critical Permissions and you press the Cancel button, you do not return to the proper page.
• It is not possible to open a database connection due to an OAuth refresh problem.
• Clicking on a review on the Analysis Results Critical Permissions page, shows an empty page.
• The OAuth scheduler to refresh an OAuth token is not working correctly.

The Authorization Box was updated on February 27, 2023. Below You will find the most important changes:

Copy Default button added to the Critical Permission page (AX/F&O)
On the Critical Permission page a “Copy Default” button has been added. With this button you can overwrite the current set of Critical Permissions and Conflicts with the default set that is provided by 2-Control. Just be careful. Using this functionality will delete all monitoring data except for the settings.

Better insight in which Approval Requests need approval
On the Requests for approval page we separated the Approval Requests in requests that need your approval and requests that you have already approved but are are pending for other approvers to give their approval.

The requests are divided over two tabs: Pending Requests and Completed Requests. When you approve a request and no more approval is needed, the request will no longer be visible in any of the two tabs. When more approvers need to give their approval, the request wil be moved from the Pending Requests tab to the Completed Requests tab where it will be visible untill enough approvers have approved or the request is rejected. After that the request will disappear from the Completed Requests tab.

Filter Security Roles based on the number of linked users (AX/F&O)
On the pages that show Analysis Results the results of type Security Role are filtered on the number of users they are assigned to. When a Security Role is not assigned to a user, the Analysis Result is now filtered out. By clicking the new checkbox “Show Security Roles with no users” on these pages, You can choose to add the Security Roles with no users to the overview of the Analysis Results.

• Inconsistent value for the Status column on the Edit Organization Role page.
• Clicking on a review on the Analysis Results Critical Permissions page, shows an empty page.
• It is not possible to add an Organization Role to a Critical Permission from a Child connection.
• Permission Set of type System shows no data when you view the Permission Set from the Object Explorer.
• The column caption on the Analysis Result pages should be Type instead of Soort (AX/F&O).
• When deleting a Master Template. it leaves the related Templates without key fields.
• Spelling errors in change log entries.

The Authorization Box was updated on February 13, 2023. Below You will find the most important changes:

Export of Organization Structure added the the Controller function profile
The AB role for importing/exporting the Organization Structure has been split in two separate roles. One for exporting the structure and one for importing the structure. This way we were able to add permission to export the Organization Structure to the Controller function profile.

Display User Name for Users that are linked to an Organization Role (AX/F&O only)
On the Organization Role page we added a new column for the User Name to the datagrid for the Users. So now both the User Id and the User Name are visible.

• Critical Permissions page shows no analyze results (AX/F&O only).
• The export of the processed Authorization Requests contains no approvers.
• An error occurs when you cancel adding an Organization Role to a User (AX/F&O only).
• No type/source type visible for analysis results (AX/F&O only).
• Revoked Permission Set can't be re-assigned immediately after revoking by using the import functionality.
• The number of approvers of an Organization Role can be modified when an Approval Group has been assigned.
• When you search for an object using the Object Explorer, searching on only an Object Id doesn't works not for all objects.
• Processed actions for an Authorization Request displays date values instead of datetime values.
• Approval Request is not fully processed, but alle approval lines have been automatically approved.

The Authorization Box was updated on February 1, 2023. Below You will find the most important changes:

Working of the “Dynamics Connection” checkboxes changed
On the Edit database page the “Dynamics Connection” checkboxes have been changed, so their working is more clear. The “Dynamics Connection unavailable” checkbox has been replaced by an icon that shows the result of the last connection test. You can no longer change the value for this field manually. When You want to disable the database connection manually, You can change the value of the “Dynamics connection disabled” checkbox.

Activate/deactivate a user using the import functionality
You can now activate/deactivate a user by using the import functionality from the Organization Chart. First You export the Organization Structure. When You open the Excel file there is a column Inactive on the tab Users. To make a user inactive, you need to enter a “x” or an “X” in this column. To activate a user, you need to clear the Inactive column. When You import the Users per Organization Role, the activation/deactivation of the user(s) will be processed.

Notes:

• When activating/deactivating a user by means of the Excel file, you can't enter an activation/deactivation date. By default, the current date will be used as the activation/deactivation date;
• When a user has several entries in the Excel file because of the different Companies or Company Groups, You need to change every Inactive column for that user to make sure the activation/deactivation is processed.

• From a child database you can't see which approvers are added to an Approval Group.
• Analysis Results for Conflicting Permissions page misses Review button (only concerns an AX/F&O connection).
• When an OAuth connection has been made and a database connection has been established, the field for the Dynamics connection doesn't show there is a connection.
• When you create a new connection, the default data is only being copied when the connection to BC is working and the Save button is pressed.
• Wrong caption in doughnut charts on Dashboard page for Agreed analysis results.
• Rows are visible for the approval settings of a user, but no data is visible.
• Import of User Data creates users when the users in the Excel sheet don't exist in Authorization Box.
• No Close button on Permission Set page when you view a Permission Set from within an Organization Role.
• When you press the Save button for the Database, you get the message “AppIds updates successfully”.
• Approval is incorrectly required when the number of approvers is set to 0, a user is being deactivated and a role is revoked.

The Authorization Box was updated on January 16, 2023. Below You will find the most important changes:

Filter on Critical Permissions that have results
On the Critical Permissions page You can filter on Critical Permissions that have analysis results by clicking the checkbox “Only show Critical Permissions to review.” This way, all the Critical Permissions that don't have analysis results are filtered off the page.

Move an Organization Role to another Department
On the Organization Role page there now is a Department field. You can use this field to move an Organization Role to another Department by changing the selected Department.

Jump to a filtered overview of the analysis results from the Conflicts page (AX only)
On the Conflicts page for AX, You can now click on the colored balls for the analysis results and this brings You to a filtered overview of the analysis results.

Changes made to the review page for multiple analysis results of Critical Permissions (BC only)
The BC version of the review page for multiple analysis results of Critical Permissions has changed to make it's functionality better/more clear. The following changes have been made:

• You get to see the same information for the analysis results on the review page as on the page you pressed the Review button,
• The button and the checkboxes for the change log entries have been removed.

• It is possible to assign approvers to an Approval Group that aren't approvers for the connected database.
• Approval Templates are not part of the parent-child construction like other templates.
• Order of Approval Groups is wrong when you delete an Approval Group that is used for an Organization Role.

The Authorization Box was updated on January 2, 2023. Below You will find the most important changes:

Better insight in the request lines that can be approved
Changes have been made to an Approval Request to give a better understanding on what to approve. Now You only see the request lines that You can approve instead of all the request lines. There is also a new State column that shows if an Approval Line has already been approved. This column is clickable, so that You can see which users can give their approval and if they have already done so.

• Number of responses of an Approval Request is wrong for an Organization Role.
• Dropdownlist for Profile ID shows two entries that can't be selected.
• Reviews of Conflicts can't be exported.
• Paging is missing in the new API.

The Authorization Box was updated on December 22, 2022. Below You will find the most important changes:

Object types removed from selectlist in Object Explorer
As part of the Object Explorer, You can select an object type to search for objects and to view the permissions on these objects. The selectlist for the object type contained types that are not used for setting up permission. These object types have been removed.

View analysis results of conflicts from Conflicts page (BC only)
This only concerns the BC version of the Conflicts page. From the Conflicts page, You could edit a Conflict by clicking the conflict name in the column Conflict. This functionality has been replaced to the Edit button at the end of the grid entry. Now when You click the conflict name, You can view the analysis results of that conflict.

Changed App ID's of Permission Sets will be automatically updated
In case Permission Sets are being moved from one extension to another, they get a new App ID. To keep the Authorization Box working correctly, Permission Sets are checked and updated automatically as part of the nightly synchronization.

Revoked Permission Set can be assigned immediately
When You revoke a Permission Set from an Organization Role, now You can assign it again immediately and You don't have to wait until the revoke has been synchronized.

Approve an Authorization Request when the creator is also the approver
When You sent an Approval Request or when an Approval Request is automatically created (by importing Organization Roles per User), the request is automatically approved if the sender is also an approver.

Description field added for an Organization Role
A Description field has been added to the Organization Role. This way it is possible to better describe the difference between Organization Roles.

Microsoft Dynamics 365 Business Center v21 support
Support for Microsoft Dynamics 365 Business Central v21 has been added to the Authorization Box. Permissions are read from the new Expanded Permissions table when the BC version is 21 or higher. This affects the following programs:

• Synchronization batches,
• Monitoring,
• Object Explorer.

Revoke approval when a user has no Approval Templates left
When the last Organization Role with an Approval Template is revoked, approval for a user is being reset in Dynamics.

• Searching for objects in Object Explorer is case sensitive for the columns Name and Caption.
• Not all default data is copied when you create a new database.
• When You use Copy default for the Critical Permissions, no Conflicts are copied
• When a Monitoring conflict is created, the reversed conflict is shown as well.
• The field Key Code in the database settings was missing.
• Enabling Continuous Monitoring for a database, results in a time-out error.

The Authorization Box was updated on November 21, 2022. Below You will find the most important changes:

Open a Critical Permission from within a Conflict
On the Conflict page there is a new button behind each Critical Permission description. When You press this button, You navigate to the Critical Permission page. When You click Close, You return to the Conflict page.

The Conflicts page for Dynamics AX is missing functionality that is available in de Business Central version of the page
New functionality has been added to the Conflicts page for Microsoft Dynamics AX. The following changes have been made:

• The multi-select of conflicts has been added.
• The New button was added to create a new conflict.
• The fields Hierarchy and Organization can be altered while editing a Conflict.

Search field added to the dropdown list for selecting Critical Permissions
A search field has been added to the dropdown list for selecting Critical Permissions. These dropdown lists can be found on the pages where You can create a new Conflict.

Status of the last analysis batch is now shown in a dialog form
The status of the last analysis batch can be viewed from the overview page and the edit page of the Critical Permissions. The status was shown in a hover text earlier and now is shown in a dialog form that can be opened by clicking the question mark button. Reason for this change, is that the hover text often became too large, causing it to fall outside the page.

The Description column on the Approval Requests page shows more information
The Description column on the Approval Requests page shows more information about the request. For instance: when the Approval Request is for a user/an Authorization Request, the column Description not only shows the username, but also the name of the user.

Exclude disabled accounts from analysis results
A new checkbox has been added to the Critical Permission page which makes is possible to include inactive users to the analysis results. The caption of the checkbox is “Analysis with inactive users.” This means that inactive users are excluded by default, which is a change in the functionality of the monitoring.

• The activation-/deactivation date is not visible for a processed Authorization Request.
• When You edit a Permission Set Object the selected Object/Object Id is not displayed correctly.
• When you try to delete a Conflict you get an InvalidOperationException error.
• The Review button doesn't work for the Analysis Results Conflicting Permissions page.
• It is not possible to revoke an Approval Group from an Organization Role using the import function.

The Authorization Box was updated on November 07, 2022. Below You will find the most important changes:

Remove button “Activate User” from User page
The button “Activate User” is removed from the User page, because the button's functionality wasn't in line with the authorization flow. All changes to a User should be done by creating an Authorization Request first.

Change log for general settings
When changing the general settings such as the Approval Settings and the Approvers, an item is added to the Change Log Entries, so that changes in these settings are made transparent.

• The “Close” button for an Organization Role doesn't work when You open the role from within a User or an Authorization Request line.
• There is no “Close” button placed on the dialog to authenticate the OAuth connection. After the authentication process you can't return to the Database page.
• User approval is not always correctly synchronized with Dynamics.
• The import of Integration Data for a user does not work.
• Changing an Approval Template for an existing Organization Role is not possible.
• Clicking the “Approval requests” button for an Authorization Request results in an error.
• Clicking the button in the “Response” column on the Requests for approval page results in an error.
• Time-out errors when opening the Monitoring - Reviews page and the Monitoring - Analysis results - Critical Permissions page.
• Error when deleting multiple Excluded Permission Sets

The Authorization Box was updated on October 24, 2022. Below You will find the most important changes:

Sort order of Organization Roles within a Department
The sort order of Organization Roles within a Department can be changed by clicking the Sort button for the Organization Role. This button is placed left of the Add button You click to create a new Organization Role. Changing the sort order of the Organization Roles works in the same way You can change the order of the Departments.

Synchronization log with error without error message
In the synchronization log You can occasionally find an error with zero error messages. This is probably because a crash has happened, and there is no clear solution to fix the problem. For this kind of error, we added a basic message saying: “A technical error has occurred. Please try again and if you keep getting the error, please contact support@2-control.nl.”

• The department order was incorrect in the export of the organization structure;
• Synchronization error “Could not clear temporary data for ManualMonitoring fullsync” resolved;
• You could create a new approval request for an Organization Role while a previous request hasn't been processed. This problem has been resolved.

The Authorization Box was updated on October 12, 2022. Below You will find the most important changes:

Authentication Method “OAuth Device Code” can't be selected for a new database
When creating a new database, the Authentication Method “OAuth Device Code” wasn't available till the page was refreshed. Therefor we changed the creation of a new database a bit. First You select the type of database and fill in the database name. When You save the database, the database maintenance page opens, and the OAuth authentication method is already available.

• Auto correct the User Security ID when Business Central and Authorization Box are out of sync;
• User can't be changed without authorization when no Authorization Roles have been assigned;
• Objects can't be added to a Permission Set (only concerns NAV2013);
• Field number of Master Template Line is not being exported/value is not being imported;
• After the import of a backup, the Approval Group checkbox disappears.

The Authorization Box was updated on 2022-09-26. Below You will find the most important changes:

Element connectionInfo added to response of GET database
The GET method of the Authorization Box WebAPI has been changed. The element connectionInfo has been added to the response body.

Authorization for the Object Explorer
The Object Explorer has been added to the roles for the function profiles so You can authorize users for the Object Explorer.

Approval request for organization role can not be approved
Existing approval requests for organization roles could not be approved after they were changed by an import. You could press the button Approve, but nothing would happen. This has been fixed.

Number of linked organization roles is incorrect
The number of linked organization roles for a user was always set to 0 and did not show the correct amount of linked roles. This has been fixed.

Export of permission reviews incomplete
The export of the permission reviews (part of the monitoring module) contained less records than visible on screen. This defect has been fixed.

Wrong presentation of column Name for reviews with a description
When You review a critical permission You can enter a description. For reviews with a description the column Name would show the value for column Description in the overview of reviews. This problem has been resolved.

Some permission sets are not shown correctly within the Object Monitor
The issue has been resolved where permission sets were not shown correctly from within the Object Explorer if they were of the type System. Also the type of permission set is displayed correctly now. Before, all permission sets were typed as System.

The Authorization Box was updated on 2022-09-13. Below You will find the most important changes:

Export / import functionality for approval groups
As part of the Backup menu the export and import functionality for approval groups has been added.

Export / import functionality for approvers
As part of the Backup menu the export and import functionality for approvers has been added.

Export / import functionality for pre and post actions
As part of the Backup menu the export and import functionality for pre and post actions has been added.

The Authorization Box was updated on 2022-08-30. Below You will find the most important changes:

Selecting a template while typing
When adding a new authorization template to an organization role You can now use “search as you type” so it is easier to select a template.

Activate or deactivate a user without an authorization request
When You want to activate or deactivate a user You need to create an authorization request. When a user has no organization role assigned and You try to process the request/send an approval request You get the error “You didn't select an organization role to process.”

An exception has been created so You can activate or deactivate a user when no authorization Role has been assigned. You don't need to send an approval request and You can simply process the changes.

Option to change the user in an authorization request has been removed
The option to change the user in an authorization request has been removed. The reason for this is that the option didn't work properly and that most users experienced its functionality as unclear.

Selectlist for templates has been expanded
When adding a template to an organization role, You make use of a selectlist to select the template. This selectlist has been expanded. Previously only the Template Description was shown, but now the Table ID and the Table Name have been added to the list.

Performance of loading table items has been improved
When adding or changing a template the table items are loaded into cache and are kept there longer so the overall performance has been improved. This should be noticeable when adding of changing multiple templates or master templates.

Authorization requests couldn't be processed
The processing of an authorization request didn't work when no approval was required. This has been fixed.

Wrong presentation of column Critical Permission Name
Only concerns Dynamics AX. The overview of Analysis Results Critical Permissions shows the User Name in the column for the Critical Permission Name. This has been fixed.

The Authorization Box was updated every two weeks on Tuesday. During this period, the main focus was on technical migrations and performance improvements. Furthermore we've introduced the possibility of OData. See below other items we've addressed:

1. Authorization Management: improved the approval experience;
2. Authorization Monitoring: improved the evaluation functionality;
3. Backend: improved error handling and performance.

The Authorization Box was updated every two weeks on Tuesday. During this period, the main focus was on technical migrations and performance improvements. Furthermore we've introduced the possibility of approval groups and central framework mangement (please contact us if you have questions about that). See below other items we've addressed:

1. Authorization Management: improved the authorization request flow and added fields and functionality for better user experience;
2. Authorization Monitoring: fixed bugs regarding the analysis functionality;
3. Microservices: improved the authorization processing functionality and import functionality.

The Authorization Box was updated on Tuesday morning November 9. The past few weeks we have been busy with technical improvements and a new module of which more later. Below you will find the main points delivered:

Export Critical Permission Analysis Results:
The Export button on the Analysis Results Critical Permissions page was not active. This has been adjusted so that the results can now be exported again.

Unknown Permission Sets:
Users in Business Central may have Permission Sets that no longer exist in that environment. These permissions were not removed when synchronizing from the Authorization Box. This has now been changed to remove the permissions not associated with the assigned organizational role. This is only the case if the setting 'Overwrite Current Permissions' applies.

Error processing template in multi-tenant environment:
An error arose when assigning an organizational role and processing the associated template data. The problem has been resolved.

Agree Configuration:
As soon as an organizational role has been linked to a Critical Permission, the results associated with the relevant organizational role must receive the review ‘Agree Configuration' in a new analysis. This didn't always happen. The problem has been resolved.en.

The Authorization Box was updated on Tuesday morning October 12. Below you will find the most important points:

Export Organization Chart including unknown permission sets:
The organization chart can be exported via Export structure. All permission sets are visible in the permission sets Excel sheet. Previously you only saw the permission sets that are also present in Dynamics. Now you also see the sets that are no longer known but that are linked to an organizational role in the Authorization Box. In Excel, the permission sets can be unlinked by replacing x with a – or by removing the x. Via the option Import permission sets per organization role, the sets that are no longer known can be processed and therefore removed from the various organization roles in the Authorization Box.

Removed database connection still counts in number of databases:
The moment a database connection is removed, it should no longer be counted in the number of applied databases. This was the case, but has now been corrected.

Error not selecting review:
If the review was not selected when assessing an analysis result, an error message was generated. The problem has been resolved.

Sorting reviews monitoring:
The sorting of the reviews has been adjusted. Most recent review is now at the top.

The Authorization Box was updated on Tuesday morning September 28. Below you will find the most important points:

Search option permission set:
On the user, the 'Search' option has been added for the permission sets section. This allows you to quickly check whether a user has a certain permission set.

Error updating web services 2016 connection:
Refreshing the web services from the Authorization Box for a 2016 environment gave an error. The problem has been resolved.

Navigate permission set SUPER from an organization role from BC18:
With a Business Central 18 connection, the permissions for the permission set SUPER were not shown when navigating from an organization role. This has been resolved.

Export organizational structure does not show link to SUPER permission set from BC18:
When exporting the Organization Chart, the Permission Set sheet did not show which organization role the permission set SUPER is associated with. This has been resolved.

Analysis details shows object info at organization role:
When assessing an analysis result on a user, the system showed object information for an organizational role. That is incorrect, this is now only displayed with a permission set.

The Authorization Box was updated on Tuesday morning September 14. Below you will find the most important points:

Attribute Specific approvers authorization requests:
The Specific approvers authorization requests attribute on an organization role has been removed. You can still set a specific approver on an organization role. The feature had no added value here.

Object 0 if object is not selected:
When adding an object for a permission set from the Authorization Box, the system returned a 0 object if nothing had been selected. This was not correct. The system now gives a message that an object must be selected.

Filter by number of analysis results AX:
It was not possible to filter within the analysis results AX connection. This has now been added. The system also filters from a critical permission if you click through on the number of analysis.

Create new AX connection:
When creating a new connection, the correct synchronization tasks are automatically created based on the customer profile.

Reviews of analysis result AX not linked:
The review on an AX analysis result was not linked, so that it was not visible. This problem is solved.

Error when assessing conflict in AX connection:
An error message arose when assessing an analysis result on an AX connection. This has been resolved.

The Authorization Box was updated on Tuesday morning August 31. Below you will find the most important points:

Object name object id 0:
An object name is now also displayed for object 0 under the Objects tab in the review screen. This depends on the type, so for example the object name 'All objects of type Table data'. The sorting has also been adjusted here so that it is sorted first by type and then by id.

Unknown permission sets:
If a permission set is included within the Authorization Box that does not exist in Dynamics/BC, then 'Unknown' is now displayed in the name. This may apply when linking to an organization role, permission set group, or as an excluded permission set monitoring setting.

Critical Permission sorting now defaults to Name:
Previously, the critical privileges were sorted by the second column on the page by default. This column concerns the calculation of the risk. The Critical Permission with the highest risk was thus shown first. The sorting has been adjusted. Now sorting is done by the Name column by default. The advantage of this is that the sorting remains the same. If desired, the calculated risk (second column) can be sorted manually.

The Authorization Box was updated on Tuesday morning August 3. Below you will find the most important points:

Buttons on database connection:
The buttons on the database connection (connection details) have been modified. The actions synchronize all, restore webservices, connector log files and test connection are located under the Database button.

Error requesting permission sets:
An error could occur when requesting the permission sets. The error has been resolved.

SUPER within BC18:
Within a Dynamics 365 Business Central 18 connection, some adjustments have been made so that the permission set SUPER is also correctly processed for the user.

System authorization with extension BC18:
When navigating on a permission set type system with extension (BC18), the associated objects were not displayed. The problem has been resolved.

Optimization synchronization log:
The synchronization log has been optimized so that the data is displayed faster.

The Authorization Box was updated on Tuesday morning July 20. Below you will find the most important points:

Import backup organization structure takes into account app ID and scope:
The import of the organization structure from the backup functionality now also checks for app ID and scope. The combination of the permission set, app ID, and scope is decisive. This allows the same permission set to be associated with an organization role multiple times. The app ID or scope will therefore have to be different.

Continuous Monitoring notification:
Within the Continuous Monitoring functionality, the notification of changes within the authorizations was sent twice. This was incorrect and has been corrected.

To review analysis result:
It could happen that an analysis result had to be reviewed if the user had also been given the right within another company. This was incorrect and has been corrected.

Checks on imports from Organization Chart:
The checks when importing the data were not always correct. The system could indicate, for example, that a business group did not exist when it did. The controls have been adjusted.

Display permissions:
Only the option Yes or Indirect is now displayed within permissions (objects in permission set). If No, the field is not filled.

The Authorization Box was updated on Tuesday morning July 6. Below you will find the most important points:

Additional information permission sets:
Two columns have been added to the permission set overview:
- No. of linked users: Indicates the number of times the permission set has been linked to a user. A permission set can be linked multiple times with one user in combination with different companies.
- No of linked organizational roles: Returns the number of times the permission set has been included in an organization role. A permission set can also be linked to an organization role through a permission set group.

Additional information organization roles:
The following columns have been added to the organizational roles overview:
- No. of linked permission sets or groups: Returns the number of permission sets or permission set groups linked to the organization role.
- No. of linked users: Indicates the number of users who have been linked to the organizational role.
- No. of linked templates: Gives (if licensed) the number of linked templates.

Additional information users:
The following column has been added to the user overview:
- No. of linked organizational roles: Displays the number of organizational roles assigned to the user.

Error by reviewing conflict:
An error could arise when reviewing multiple analysis results conflicting critical permissions. This error has been resolved.

Execute on yes on linked object:
When linking an object to a critical permission, it could happen that the object type table data was set to Yes for execute rights. This was wrong and has now been corrected.

Notification if not set as approver:
In the Requests for approval screen, all approval requests are visible. The application can be reviewed via the eye. If you are not set as an approver for the relevant type, you will not be able to view this request. The system now gives a message, for example: You have not been created as an approver for requests of the type 'Assign authorizations'.

Link Dashboard Administrator:
When linking the dashboard, an error message could be displayed. The problem has been resolved.

Sort screen Request for approval:
The data in the Requests for approval screen is now sorted by Created on.

The Authorization Box was updated on Tuesday morning 8 June. Below you will find the most important points:

Manage permission set from the Authorization Box:
It was already possible to create a permission set from the Authorization box within the recording functionality. Now it is also possible from the permission sets overview. A new permission set can be created here via the 'New' button. The objects (permissions) can also be linked or edited to the set. In Dynamics NAV it is possible to create or change all sets of the type 'System'. Extensions cannot be modified. Within Business Central, only the sets of type 'User Defined' can be created or modified.

Notification:
When analyzing critical permissions it is desirable that the system provides a notification as soon as the analysis has been performed. This was no longer immediately visible by increasing the notification number. The problem has been resolved. The condition is that the notification setting is active.

Data when editing organization role in authorization request:
An organization role to be deleted can still be edited before requesting approval. The system did not show the correct data. This has been adjusted so that the correct data is now shown. Only the end date can be changed.

The Authorization Box was updated on Tuesday evening 25 May. Below you will find the most important points:

User data based on employee number:
With our module “User Templates”, templates can be set up for, among other things, creating and filling user-related data. For example, based on a template, the User Setup can be filled, the table Salespersons/Purchasers, Resource, etc. The data that the system uses for this can be specified in the authorization request under User data. Here you can also select the Employee number from the Dynamics/BC environment. After selection, the available fields of the Employee from Dynamics/BC are transferred to the Authorization Box.

Error adding subscriber Continuous Monitoring:
When adding a subscriber to a Critical Permission, the system returned an error if this user had not yet set any notifications. This issue has been resolved.

Copy Critical Permissions by default:
Under monitoring, Critical Permissions, our default configuration of Critical Permissions must be taken over by default via the Copy button. This no longer worked, but has now been restored.

The Authorization Box was updated on Tuesday morning 11 May. Below you will find the most important points:

End date mandatory when revoking an organizational role:
It was possible not to specify an end date when revoking an organization role. This has now been made mandatory.

Link organization role to critical permission:
When approving the analysis result by organization role, the system asks if you want to link the organization role. This must be performed with “Yes”. This did not happen, but has now been resolved.

Rejected Permission Sets Organization Role:
When an authorization request for an organization role is rejected, the new permission sets are given the status “Rejected”. After processing the organization role, these sets must be deleted. The system did not do this.

The Authorization Box was updated on Tuesday morning April 13. Below you will find the most important points:

Processing authorizations:
The processing of authorizations took a lot of time. Several adjustments have been made to fix the problem.

Deleted user sync:
The authorizations of users deleted in Dynamics are no longer synchronized. As a result, you will no longer see these users in the synchronization log.

Setting “Default Override Current Permission”:
The “Default Override Current Permission” setting was previously available under general, customer details. This setting has been moved to database level. You can now set this per database connection. The setting is adopted at user level. When changing the setting at the database level, the system asks whether this setting should be applied to all users.

Merge data for import users per organization role:
If, when importing users per organization role, multiple organization roles apply to one user, they will now be bundled into one authorization request. This was not the case.

Permission set and users:
All information must be available on the detail page of a permission set. Linked objects, users, organization roles, and permission set groups. Due to an error, nothing was displayed among users. This has been resolved.

Remove company from company group:
If a company is removed from a company group, this will have an impact on all users to which this company group. This was not implemented correctly in all cases. The problem has been resolved.

The Authorization Box was updated on Tuesday morning March 30. Below you will find the most important points:

Automatic logout:
You were not logged out automatically if there was no activity. This was not correct. After 30 minutes of inactivity, you will now be automatically logged out.
Did you know that you can also authenticate with Microsoft authentication? Contact us for more information.

Setting Dynamics connection disabled:
It has been made possible to disable a Dynamics connection. As a result, there is no unnecessary synchronization and no errors if, for example, the environment is not available. Switching off can be practical, for example, if a test environment is no longer used for testing authorizations.

Reject approval request:
An error arose when rejecting an approval request for a company group. This has been resolved.

Column layout Organization roles:
The order of the columns under the Organization Roles tab for a permission set has been adjusted. Now the name of the Organization Role is displayed first, followed by the Organization Chart.

Organizational Role Approvers:
The Approvers screen also contains the Organization Role column. This remained empty even if specific approvers have been set up for an organizational role. This has been adjusted. Specific approvers are set up on the organizational role itself.

The Authorization Box was updated on Tuesday morning March 16. Below you will find the most important points:

General:
The last sprint was dominated by solving various minor issues and the further development of the Authorization Box.

Notification when processing:
When processing a changed organization role, permission set group, business group, or authorization request, the system will now notify you that it is processed in the background and that you can see the result in the synchronization log.

Page Synchronization Log:
The synchronization log has been adjusted. It is now possible to set how many records you want to see and a Refresh button has been added to update the page with the latest data.

Link to database connection:
The notification for an error in the Dynamics connection contains a link to the Database connection. This link did not work. This has been resolved.

Company Group status:
When a company was removed from a group, it was given the status “Modified”. This was incorrect and has been changed to “To be removed”.

The Authorization Box was updated on Wednesday morning February 17. Below you will find the most important points:

Create NAV UP user via authorization request:
Creating a new user via an authorization request resulted in an error. This has been fixed.

Permission set object types:
Objects of type 14 and 15 can be linked to a permission set. Previously, this gave problems. This has been resolved.

Delete authorization request:
Authorization requests created through the import could not be deleted from the authorization request. The system reported that you were not authorized. This has been adjusted so that these new authorization requests can still be deleted.

Missing Dynamics User Message:
The system gave a message if the system could not synchronize a user because they are not present in Dynamics/BC. This notification was unnecessary and will no longer be sent.

Processing to Dynamics/BC:
With the February 2 release, processing to Dynamics/BC is performed in the background. In some situations this processing could take a lot of time. This has been optimized so that the data must be processed within minutes. You can see the status of this in the synchronization log under menu user management.

The Authorization Box was updated on Tuesday morning February 2. Below you will find the most important points:

Processing authorizations to Dynamics / BC:
When processing an authorization request, the permission sets associated with an organization role are also assigned to the user in Dynamics / BC. In the new situation, this processing is performed in the background. It is therefore possible that the result is not immediately visible in the Authorization Box. If changes have been processed, the system creates a synchronization log record. This shows the basis on which the synchronization took place (for example an authorization request) and for which user this was done.

Delete Authorization Request:
In the authorization requests list, the delete option is only available if the request has the status New or Canceled. It is also possible to delete the authorization request itself if it has the status New or Canceled.

Message when company group is deleted:
A business group can only be deleted if it is not in use. The system will check this and indicate in the message why the company group cannot be deleted.

Message when deleting permission set group:
A permission set group can only be deleted if it is not in use. The system will check for this and indicate in the message why the permission set group cannot be deleted.

Error removing objects from critical privilege:
When removing objects from a critical privilege, the system returned an error. The problem has been resolved.

The Authorization Box was updated on Tuesday morning, January 19. Below you will find the most important points:

Display Permission Sets & Columns:
On the page with all Permission Sets, the column names were shown in English with the language set to Dutch In addition, the permissions under a Permission Set were displayed incorrectly. This has now been resolved.

Error in backup Organization Chart:
Importing the Organization Chart resulted in error messages that prevented the Excel being processed. This has now been resolved.

Error message in “harmonica” after activating / deactivating user:
When a user was activated / deactivated, an error message was displayed in the processed authorization requests under the “harmonica” Organization Roles. This has been resolved.

Response notification Authorization Request:
The mail and notification that people receive after approving an Authorization request have now been adjusted.

Incorrect review screen, Conflicting Permissions:
Under the harmonica “Analysis Result Conflicting Critical Permission’ when clicking through the “Review eye”, user were redirected to incorrect review screens This has been resolved.

Delete Permission Set shown as “Change”:
When removing a Permission Set from an Organization Role, the request indicated that the Permission Set was modified instead of deleted. This is now shown as type “Delete”.

The Authorization Box was updated on Tuesday morning January 5. Below you will find the most important points:

Error message when cancelling authorization request:
The system returned an error when cancelling an authorization request. The error has been resolved.

No notification after import from organization chart:
As soon as the import of permissions per organization role or users per organization role has been processed, the system must provide a notification. This did not happen. The problem is solved.

Reject approval request:
Under the function profile of the Controller, an approval request could be rejected. However, this gave an authorization notice. The right has been added to the function profile.

Profile ID in request for approval:
An incorrect profile ID was displayed in the approval request. The problem has been resolved.

Dynamics change log entries:
Within the analysis results, the column “No. of change log entries” has been added. This information can be important for analysis results at user level. It indicates whether the user has made changes to the analyzed data in Dynamics. The functionality itself was already available in the Authorization Box and is now shown in more places.

The Authorization Box was updated on Tuesday morning, December 15. Below you will find the most important points:

Incorrect display when deactivating user:
When a user was deactivated, the tick ‘Activated in Dynamics’ was not removed in the user overview. The user card did show that the user was deactivated. The incorrect display in the overview has now been adjusted.

Fixes for Critical Permissions:
An error message was displayed when saving Critical Permissions. In addition, it was not possible to review multiple Critical Permissions at the same time. These issues have now been resolved.

Conflict results:
Clicking the Conflict results brought up a blank screen without showing the results. This has now been resolved.

Incorrect Organization Role display:
When clicking through to an Organization Role in an authorization request, the screen of the Organization Role was displayed incorrectly. This has now been resolved.

Adjustment notification processing Organization Chart:
When importing the Organization Chart ‘Users per Organization Role’ the notification message was given that Permission Sets have been assigned or revoked. Instead of Permission Sets, Organization Roles had to be shown. This has now been adjusted.

The Authorization Box was updated on Tuesday morning December 1. Below you will find the most important points:

Deactivate / activate data user:
A user can be deactivated from the Authorization Box where a date from and a date until can be specified. This data was not reflected in the approval request. This has been adjusted. The same goes for activating a user.

Controller function profile:
The function profile of a controller in the Authorization Box was incorrect. In the approval request was not all the information visible. This has been resolved.

Review date filter:
Analysis results can be reviewed. The reviews can be found in the menu Monitoring, Reviews. It is possible filter the reviews by date (from).

Use web services for data in BC365 cloud environment:
The setting “Use web services for data” in a database connection with a BC16 / BC17 environment gave an error. This bug has been resolved.

The Authorization Box was updated on Tuesday morning November 17. Below you will find the most important points:

Authorization request for Windows User:
Creating an authorization request for a new user by selecting the Windows user went wrong. The request that was created could not be mutated. The problem has been resolved.

Profile ID not visible on organization role:
Within the organization role overview, the linked Profile ID was neatly displayed. On the organization role details the field was empty. This display issue has been resolved.

Analysis result organizational role:
If an object to be analyzed was linked to an organization role via a permission set group, the organization role was not included in the analysis result. This bug has been fixed.

UNKNOWN in change log entry:
The description of the change log entries sometimes contained the text UNKNOWN. The problem has been resolved.

Notifications and email:
The notification and email for an approval request and response for an adjustment to an organizational role is supplemented with the department under which the organizational role falls.

The Authorization Box was updated on Tuesday morning November 3. Below you will find the most important points:

Open last message:
The number of unread messages is shown at the top right next to the envelope. All messages are opened via “Read All Messages”. This screen did not immediately display the most recent message. This has been restored.

Continuous Monitoring:
With Continuous Monitoring you can be kept informed by the system of changes within authorizations. Technical improvements have been made within this module.

Error opening user:
An error could occur when clicking through to the user. The problem has been resolved.

Approval request information:
Changes to an organization role may require approval depending on the approval settings. However, the changes were not shown in all cases in the approval request. This has been adjusted so that the changes are shown based on the change log entries.

Export Processed Authorization Requests:
After selecting processed authorization requests, they must be exportable. A blank screen was shown for this action. The bug has been fixed so that now the export works.

Permission Set Status in Organization Role:
When a permission set was deleted in an organization role, it was given the status “Changed”. This was incorrect and has now been changed back to “To be deleted”.

Date / time in changes:
The time in the changes shown on an approval request was two hours behind. The problem has been resolved.

The Authorization Box was updated on Tuesday morning October 20.Below you will find the most important points:

Help Authorization Box:
Via your e-mail address (top right) and then Help, you can navigate to the online help of the Authorization Box. We have updated the 2-Control Online Software Help and it is now written in DokuWiki.

Responses within processed requests:
Within the processed authorization request, we have added a Responses (approval entries) tab. Below this tab you can see which user has approved the authorization request, if applicable.

Screen Record Permission Set:
Within the screen with the recording parameters, we have made a number of improvements so that it is only possible to start a recording after everything has been set correctly.

Navigate by organization role:
When navigating an organization role from the user or an authorization request, the correct screen was not displayed. The problem has been resolved.