User Rights Management

<< Back

Tight security is essential in a business system, and more so in a multi-user, multi-branch environment for a business application. Wings offers powerful User Rights Management enabling you to manage multiple users across multiple locations and giving and denying individual users rights over the software in a most detailed manner.

Users

You may 'create' and manage as many users as you are licensed to. One or more users may have Administrator level rights and others may have User level rights.

Administrator Level Rights

An Administrator has full access to the software and its data. An Administrator has the following rights:

• To create and give rights to individual users
• To create, edit and manage masters
• To configure the software using Feature Management and other settings
• To specify which modules, transactions or reports should be used by users
• Apply authorisations to transactions
• To set permissions for transactions and reports to configure, edit, print, etc.

User Roles & Users

The Administrator may define and identify individual users with respect to their tasks. He can maintain a hierarchy of users with the help of user roles and users.

• Define and identify users by their roles such as Administrators, Stores Manager, Finance Manager, Accountant, Cashier, etc. You may maintain as many as roles as required.
• Create multiple users of the software.
• Assign roles to each user, so that they get access to only authorised parts of the software
• Maintain unlimited groups for user roles and users in Tree form
• Define branch-wise users along with their roles

User-Wise Transactions And Reports

Wings enables you to assign only those transactions and reports to users which they are authorised to use. Each user will see only authorised masters, data entry screens and reports.

You may assign all or some masters, transactions and reports from a pre-defined list.

Permissions

Individual users may be given or denied rights to perform specific actions on individual transactions like Save, Edit, Print, Configure, Draft, Template etc. This ensures more secured data entry and data storage. For example, a user without having edit permission can only save a transaction, but cannot modify saved data.

You may grant or revoke permissions to reports like Access, Configure, Print, Sort, Group, etc.

Control Drop Down Lists

In an online environment, you may wish to allow personnel of any Branch to view only those masters such as customers, suppliers, products, currencies, etc. which are branch or location specific. Wings e-Biz helps you achieve this by configuring drop down lists for any transaction. You may:

• Assign related security groups to user roles.
• Grant permission such as View, Edit, Rename, etc. for masters falling under assigned security groups.
• Specify permissions to only those properties of masters which users are authorised to access or see.

Transaction Authorisation

Control the usage of transactions by users, by applying authorisation levels and sequences to fields or columns. For example, you may wish not to allow users to bill more than a certain limit of amount.

User Level Security

Wings provides the flexibility in configuring transactions and reports of any product or module for more secured usage of the software and data.

You may make:

• Fields non-editable
• Columns non-editable
• Hide fields/columns

You may apply such configurations for every user, and such changes remain for future use.

Multi-Location

Wings does much to help you manage systems in a multi-branch environment. You may:

• Set branch specific users. Segregate users with respect to each branch, location, project site, etc.
• Assign only those modules (masters, transactions and reports) for individual branches.
• Allow users to access only those masters which they are authorised to see
• Control and filter values of any drop-down lists
• Have different security groups for customers, suppliers, products, currencies, etc. of any master and grant group-wise access to users of different branches.
• Gain total control of which users can view or alter the data.
• Provide authorisation for transactions for any branch, location, project site, etc.

<< Back