Authorization Types

Workcube is a role-based system. Each user has at least one role/position. Special privileges can be defined for each user.

Authorization Types

• Menu Authorization
• Module Authorization
• WO - Page Authorization
• Registration Restrictions
• Company Authorizations
• Fiscal Year - Term Authorizations
• Branch Office Authorizations
• Warehouse Authorizations
• Transaction Category Authorizations
• Process Stage-Workflow Authorizations
• GDPR Authorization

Menu Authorization

Route: Dashboard > Settings > Authorization and Interface > System Menus

There is a standard menu in Workcube. Besides the standard menu, the menus can be customized. Thus, users can access different menu options.

Warning: Standard and custom menus are set by system administrators. For applications and information that you cannot access or should not see, contact your system administrator.

Module Authorization

Route: Dashboard > Settings > Security > Authority Groups

Module authority determines which modules a user can access and is set under the authority group. Users (roles) included in each authority group can access modules authorized in that authority group. A user who is not authorized to the module cannot access the business functions of that module.

Power-user authorization is set for each module. An authority group user with Power User authority can make the parameters, data conversions, language settings, first level screen edits of that module.

WO - Workcube Objects Business Functions Authorizations

Route: Dashboard > Settings > Security > Authority Groups

Workcube business functions mostly consist of more than one screen. For example, the Order business function is a WO. A WO often has multiple events screens such as new registration, list, and update. The specific powers to be granted to a WO are determined under the "Authority Group". WO can be given viewing, adding, updating, and deleting rights. 

If the unviewable checkbox for WO is selected, this WO will not appear in the menu. Even if the URL address is typed in the browser, the page is blocked. The user is warned as "Unauthorized Access Request" and the action is logged. The "Update" button for the update authority, the "Add-Save" buttons for the addition, and the "Delete Record" buttons for to delete authority.

Role-Based Page Permissions

Route: Dashboard > Settings > Security > Employee Authority Restricted Pages

In Workcube, special authorization can be given to a user as an exception from the authorization group. A page restriction can be given on the position of the employee by selecting an employee. For example, special authorizations such as the ability to save orders and view offers can be arranged in the sales module.

Registration Exceptions and Authorizations

This is an issue related to some operations in Workcube. It is a constraint in some places in the system that allows two or more people not to delve into the same form at the same time. Thus, it is prevented that different people cause data loss when making changes on the same detail information. 

For example, one of the screens, where this restriction is applied, is the contact detail screen. If two personnel users could enter this screen to make changes to the different information of the same person, then only the information entered by the last recorder would be processed into the database, thus the other employee who thought he was doing his job would cause data loss. In the current situation, if one of the staff members enters this screen and the other tries to enter the same screen, they are warned that this page is used by the other user, and they are prevented from entering the screen.

Branch Office Authorization – Special Code Authorization

Persons in the operation can only make transactions related to the branch offices defined for them. A person can be assigned as many branch office authorizations as desired from the position detail. But if a special code is defined in the system, then this authority is restricted. For example, if a staff member is authorized to transact in a branch office, but at the same time, a special code of the driver position is defined for him, that person can see only the drivers in that branch office and make transactions.

Term – Company Authority

This authorization also allows the given person to make transactions only in the selected accounting periods. In addition, there is a date restriction here, if such a date limit is set, then the person can only make transactions after that date when he is authorized.

Process Transaction Authorization

Process management allows the records made in Workcube to be managed within certain authority or authority groups. The record desired to be made with a defined process on a certain form follows the process stages and performs dynamically defined transactions at each stage. Process authorizations are based on group architecture. You can define more than one authority group during the process stages and assign the positions you have determined beforehand to these authority groups. Thus, a position may be authorized at one or more stages of one or more processes.

The user-triggered process alerts the next user authorized in the stages. It sends informative warnings to the positions defined within the groups. As an example of process management, we can give a product registration process. For example, you can authorize one person to save only the basic information of the product, another to save only the accounting code, and another to activate the product. And these authorizations can be defined in an order that cannot be passed to the other before one ends.

One of the most important authorization examples in Workcube is this process authorization. From the moment you log in to Workcube, your authorizations are determined. During the usage period, transactions can be made within the limits of these authorizations. Some of these authorizations are kept in memory and some in the database. According to this, your every move is determined sometimes with instant control, sometimes as you enter, and borders are drawn accordingly. For example, the menus you see when you log in are unique to you and you can only see the titles within your authorization. Sometimes, when you try to enter a page, a text that warns you will appear and say that you are not authorized. This is a current control result.