Understanding roles and access rights
In functional terms, a role is a capacity in which a user makes use of a USoft application.
DDL rights
DDL rights are the rights to Create, Alter and Drop database tables, that is, tables known to the RDBMS.
Table rights
A table right is an access right that gives users access to data in a table or Logical View defined in the application itself, as opposed to: defined in consumed modules (access to the latter is given by module rights).
Column rights
A column right is an access right that restricts a table right by making an exception for a specific column.
Role conditions
A role condition is a SQL condition attached to a Table Right.
Access rights for different table types
The USoft Definer catalog shows table objects as belonging to different types: database tables, subtype tables, Logical Views, component tables, and interface tables.
Access rights for supertypes and subtypes
Access rights on subtypes require special consideration. For example:
Job rights
A job right is the right for a runtime user to execute (call) a job defined in USoft Definer.
Component rights
A component right is the right for a runtime user to execute (call) methods from an RDMI component defined in USoft Definer.
Module rights
A role can have module rights on another role in a provider module. A module right gives access to all the resources that the module role has access to.
First Menu Pages of roles
In the 2 USoft GUI tools (USoft Web Designer and USoft Windows Designer), you can define that a menu page is First Menu Page of a role.
Testing roles and menus
This help topic is an overview of different ways in which you can switch between different users, roles and menus in Development.
Schemas and extension properties
With schemas and extension properties, you can make available application-specific runtime properties for the application, for roles, and for users.