Operations Registry entry

Assign permissions to users / groups on a per table basis.

Usage

This Registry entry can be assigned to users and groups:

Key User User Group Group Group Group
Key 1 User User Group Group Group Group
Key 2 user user group group Default Default
Key 3 Table Table Table Table Table Table
Key 4 table Default table Default table Default
Key 5 Operations
Value priv;priv;...

where:

priv;priv;... is a semicolon separated list of permissions:

daDefaults

Define sets of default values and change the set of default values currently used.

daDelete

Delete records from the module(s) specified in Key 4.

daDesign

Create new reports.

daDisplay

Display records from the module(s) specified in Key 4.

daDittoAll

Use the Ditto All Fields (SHIFT+F9) option on the Edit tab of the Ribbon.

daEdit

Edit records in the module(s) specified in Key 4.

daEditHelp

Edit the field level help description.

daEditQuery

Edit the search criteria of the previously run search in Texql format (see Other Search functions for details).

daExport

Use the Export Schedules facility.

daImport

Use the Import tool.

daInsert

Add new records to the module(s) specified in Key 4.

daMerge

Use the Merge Records tool.

daQuery

Search the module(s) specified in Key 4.

daRecall

Use the Record Recall facility.

daRecondition

Use the Condition Update tool.

daReidentify

Use the Reidentify tool.

daRelocate

Use the Relocation tool.

daReplace

Use the Global Replace tool.

Note: Users with the daReplace Operations privilege do not also require the daRecondition, daReidentify, daRelocate or daRevalue privileges in order to have access to the tools associated with those privileges.

daReport

Generate reports.

daRevalue

Use the Revaluation tool.

daSecurity

Edit Record Level Security permissions.

daTemplates

Create a Record Template in the module(s) specified in Key 4.

Tip: Think of da as "define access".

The Operations and Table Access Registry entries work hand in hand: the Table Access Registry entry determines which tables (modules) a user / group is permitted to access; the Operations Registry entry then determines what actions the user / group is permitted to perform on records in the table.

Note: There must be an Operations Registry entry for each table to which the user / group has been granted access through the Table Access Registry entry.

Examples

This entry specifies permissions for the Admin group on all modules:

Key Setting
Key 1 Group
Key 2 Admin
Key 3 Table
Key 4 Default
Key 5 Operations
Value daQuery

daDisplay

daEdit

daInsert

daDelete

daReplace

daDefaults

daReport

daDesign

daEditQuery

daEditHelp

daSecurity

daImport

Note: If the permissions are the same for all tables, enter Default in Key 4 instead of the name of a table. This will reduce the amount of Registry entries required for a group.

The Volunteers group are only allowed to search, view and edit Parties records:

Key Setting
Key 1 Group
Key 2 Volunteers
Key 3 Table
Key 4 eparties
Key 5 Operations
Value daDisplay

daQuery

daEdit

Note: If daEdit privilege is not provided, all fields in records returned by a search will be read-only (they will appear greyed out). To restrict users to editing only certain fields, provide them with the daEdit privilege and use the Column Access Registry entry to restrict access to required fields.