On the Access rights tab, which is present when you have selected a new or existing task for a data source in an application in the Application browser, you can restrict the visibility and use of tasks in this data source, dependent on the user (login name in Windows) and its assigned role.

Click here for information on how to edit properties in general. On the current tab you'll find the following settings:

Access

Here you may define which Roles have which Access rights to seeing and using this task. You can indicate for each role whether no access (None), Read access (None and Read both hide the task), Write access or Full access must apply (Write and Full both show and allow use of the task). Access rights for a role associated with a task in the application setup can never supersede access rights for the same role associated with a dataset or database in the database setup. If a role is not linked to this task, then each user linked to that role has full access by default. If no role is linked to the task, every user linked to a role has full access. A user without a role always has full access. Users are assigned to roles in the application setup.

From Collections 1.12.2, if a task adapl uses LOCK, WRITE and/or DELETE FACS operations in the current (_LOCAL) or other databases, then those will only executed if the user role has write access (or full access if DELETE is required as well) to the relevant .inf: the role access rights to the current data source are not relevant for these operations (while in older versions of Collections they erroneously were).

See also

Security in Collections