Scope

A Table Right or Column Right has foreground scope if it has the setting "Privilege Scope = Foreground and background".

Foreground scope gives the holder the right to perform both foreground access and background access on that table or column. "Access" in this context involves both

•Data retrieval (SELECT, in SQL terms) and

•Data manipulation (INSERT, UPDATE, DELETE, in SQL terms).

Foreground access includes all forms of access other than:

•Access by a constraint, as an indirect result of a user action.

•Access by a corrective relationship attribute setting as an indirect result of a user action. Corrective relationship attributes are Delete Rule and Update Rule settings other than Restricted (ie., Cascading or Nullify).

This obviously includes many direct forms of access, such as data retrieval and manipulation through USoft windows and web forms mapped directly to tables, and access through SQL statements executed from SQL Command dialogs. But foreground access ALSO includes many forms of access that you might think of as being more indirect, for example:

•Accessing underlying tables when using a Logical View.

•Accessing data by calling USoft Batch jobs.

•Accessing data by calling USoft REST service methods.

A Table Right or Column Right has background scope if it has the setting "Privilege Scope = Background only".

Background scope gives the holder the right to perform background access on that table or column. "Access" in this context involves both

•Data retrieval (SELECT, in SQL terms) and

•Data manipulation (INSERT, UPDATE, DELETE, in SQL terms).

Background access includes:

•Access by a constraint, as an indirect result of a user action.

•Access by a corrective relationship attribute setting as an indirect result of a user action. Corrective relationship attributes are Delete Rule and Update Rule settings other than Restricted (ie., Cascading or Nullify).

A Table Right or Column Right has no scope if it has the setting "Privilege Scope = None".

This denies the holder the specified right. But the holder is also denied every right that is not specified in the first place. There are only 2 use cases for specifying Scope = None explicitly:

•For Column Rights, specify rights with Scope = None in order to restrict a Table Right by overriding (denying) that right at the column level.

•For Table Rights, depending on your project preferences, you may decide (as a standard) to have a Table Right record for each usergroup for each table. This approach could make it easier to trace and control that a given Table Right is granted or denied. If you use this strategy, set Scope = None for Table Rights that are denied.