Effects of Mark as Options for Views, Tabs, and Tables

When you are in Security Setup mode, you can change the security settings of views, tabs, and tables using the Mark as security options. If you mark a view, tab, or table as editable, read-only, or not accessible, the security settings for the attributes, relationships, and pages contained within that element might also be changed. Which items are affected depends on the default security level of the profile, which Mark as option is selected, and the relationship of the class owning the attribute or relationship to the class that owns the view or table.
Note: The security settings for actions are not affected when using these options.

Backing Up Your Work

When setting security on views, tabs, and tables, the system might create security overrides for many classes, attributes, and relationships at once. There is no ‘undo’ option for this feature. For this reason it is a good idea to save copies of your profiles as you work. For example, if you edit one area to react the way that you want in a profile, save a copy so that you can return to that stage if necessary.

Attributes and Relationships that Appear in Multiple Views

When working with view, tab, and table security settings, know that some attributes and relationships appear in multiple views, tabs, and tables. Therefore, if an attribute or relationship receives a security setting in one view, and you then apply another Mark as option on another view, tab, or table where the attribute or relationship appears the security setting may change. The most recent edit always applies.

Security for Table Columns

In Security Setup mode, you can set security in individual columns in a table. When you do this, the attribute or relationship represented by the column is secured, as well as the relationship represented by the table that contains the column.
Note: The attribute or relationship represented by the column will have the same security level wherever it appears in the user interface.

Summary of Effects of View, Tab, and Table Security Settings

The following tables show the effect of each Mark as security option when used on views, tabs, and tables. There is one table for each of the three default security profile settings. Only changes from the profile’s default setting are listed. For example, if you are in security setup mode for a profile with a default setting of Editable, selecting Mark as Editable on a view, tab, or table will not cause any changes to the profile (unless objects contained there were previously overridden).
Note: When setting security on a view, tab, or table, security is set for all of the attributes and relationships visible in all of the configurations, including any administrator configurations that have been created.

Default Security Level: Editable

Set to No access1

1
Only the relationship that is represented by the table is set to No access.

Default Security Level: Read-only

Set to Editable 1
Set to Editable2
Set to No access3

1
Attributes owned by the class represented in the view, tab, or table are set to Editable. All other attributes are left as Read-only.

2
The relationship that is represented by the view, tab, or table is set to Editable. All other relationships are left as Read-only.

3
Only the relationship that is represented by the table is set to No access.

Default Security Level: Hidden

Set to Editable or Read-only1
Set to Editable or Read-only2

1
Attributes owned by the class represented in the view, tab, or table are set to Editable. All other attributes are set to Read-only.

2
The relationship that is represented by the view, tab, or table is set to Editable. All other relationships are set to Read-only.