Views - View Permissions
Expanding the Views section reveals the View Permissions
listing. Clicking this button brings up the View Permissions screen. This screen allows you to see and alter access to particular users, groups, and views. The screen looks like this:
Group membership generally determines access to, and permissions for, views. Permissions may also be set for individuals, with access rights that differ from the rest of the group.
Default permissions are set in the Views section under the Connection tab. These permissions (and therefore access to the view) can be extended to the user, or they may be modified on a per-user or per-group basis.
Once you click on a user or group, the Add Access button
will become active. You can use this button, or simply place a check in the checkbox next to the user's name, to provide extended access to that user or group.
To grant permissions by view:
- Expand the Views section in the left pane.
- Select the View Permissions section.
- Choose the Select by: View radio button.
- Select the view of interest from the dropdown list.
- Check or uncheck each User Name or Group Name to indicate whether they should have permission or not.
- Click the Update button
in the toolbar.
To grant permissions by user or group:
- Expand the Views section in the left pane.
- Select the View Permissions section.
- Choose the Select by: User/Group radio button.
- Select the User or Group of interest from the dropdown list.
- Check or uncheck each view to indicate whether permission is allowed.
- Click the Update button
in the toolbar.
Overriding Defaults
Permissions can be overridden by highlighting a view or user with permissions to that view, then changing the configuration of the view as necessary. The only items that may not be changed are the SQL statement and the type of list. Items that appear in the list may be overridden.
The following are some examples of permission overrides. This is not an exhaustive list, but rather some illustrative examples.
Overriding Access Permissions
A supervisor may need to change a description of a work order, and this access may not be desired for a worker. In this case, the default permissions may be set to make the description field a Readonly in the Field tab. Then, the administrator can open the view in the View Permissions section and open the view for the Supervisor group and deselect the Readonly checkbox in the Fields tab, then set the default permissions on the Connection tab to allow updates.
Overriding Visible Fields
Some fields may not be necessary for a particular group of workers. Someone stocking the inventory need not see the price of each item, as this may clutter the view with too many fields. A salesman using the same view will need the price field. The field can be enabled for the Salesmen group, and marked as invisible for the Stock group.
Overriding List Items
Although list types are set by the initial configuration of the view, the items in the list may be changed to suit a user or group. A group based in one warehouse may not need to use the inventory in another warehouse, therefore their list of item descriptions can be limited to just their warehouse.
|
To override a list type value list for a field:
|
The static list can display additional information to the right of the list of values. To create a two column list, separate the value from the additional information with the pipe character:
Example:
Overriding Filters
The data which appears as part of the view may be changed per user or group by adding or altering the filters which appear in the Filters tab. This may be used to limit the inventory that appears to only that which is in a particular storeroom, or may limit work orders to those assigned to a particular supervisor.
Overriding Display Name
Display names may be altered for a specific user or group by editing the Display Name field in the Fields tab. The staff that places orders may refer to an item by a UPS number, while the staff that pulls the inventory may refer to an Item number. This is the same number in both cases, but it has a different name for each application. The Display Name can be changed in this case to avoid confusion.