Company security views

Security

Security views determine what a user can see for a particular system or company resource. For example, at the system level you might want to limit which of your companies a user can see. At the company level, you might want to restrict a user from seeing payroll data for executives. Multiple users can be assigned to a security view.

Security view restrictions are based on user-defined conditions. While a permission can grant access to a resource, a security view can limit the scope of that access.

Example

Company security view. Suppose a user has access to the Employees resource but you want to restrict their access to only those employees whose marital status is married. You could write a condition that states that users with the security view can only view information for employees for which marital status equal married. Information for unmarried employees would not be available to users assigned to the security view.

Multiple security views on a single resource can be assigned to a single user. This means you can assign security views to a user based on exactly what the user is allowed to see. The behavior of security views on a resource can be summarized as follows:

  • If no security views on a resource are assigned to a user, the user can see all rows (if the user has appropriate permissions).
  • If one security view on a resource is assigned to a user, the user can only see the rows determined by the security view.
  • If multiple security views on a resource are assigned to a user, the user can see the rows determined by any of the security views.

Company security views are created by a system administrator or a company administrator in the [Company Name] > Administration > Security > Security Views subfolder. You can assign authorized users to a security view on the Users tab of the Security View window or you can assign a security view to an authorized user on the Security Views tab of the Authorized User window.

Selection conditions which refer to the items in a securable folder automatically apply the folder's security views. In particular, selection conditions can reference security views. This means that you can create security views which reference other security views and automatically apply changes to a referenced security view to the referencing security view.

Example

You can create a security view on payroll checks that limits by a user's security view on employees. If the security view on employees changes, it is automatically applied to the security view on checks.

Extras\Payroll\PR Security Views for allowed employees.xml; Extras\Human Resources\HR Security Views for allowed employees.xml
×

Security views security

Common accesses available on security views

Access A user with this access can...
Change Use the mass change action on security views.
Custom Fields Create and edit custom fields for security views.
Data Have read-only access to security views from anywhere in the software (e.g., field validations, filters, date expressions).
Delete Delete security views.
Edit Edit security view records.
Export Export security view records from ActivityHD.
Import Import security view records into ActivityHD.
New Create new security view records.
Read Have read-only access to security view records.
Report Run reports with security view information.
Report Designs Create and edit report designs with security view information. This access enables the Report Designs button on the Output tab of report dialogs.
Shared Answers Create and edit action profiles and report profiles related to security views.
Shared Filters Create and edit shared filters on security views.
Visible View the Security Views folder in the Navigation pane.

 

×

Report Email dialog

From
The email account from which to send the email. Valid options are:
  • Windows user default account. Sends email using the user's Windows default email account. For most users, this is the account configured in Outlook or another email client application.
  • Server personal. Sends email using the email configuration for the system or company server and the email address on the current user's authorized user record. The authorized user record must have a confirmed email address.
  • Server generic. Sends email using the email configuration and "from" address for the system or company server. This option requires "Send generic" access to the Server Email resource.
To
The email address(es) to which to send the email. Separate email addresses with semi-colons.
CC
The email addresses to copy on the email. Separate email addresses with semi-colons.
BCC
The email addresses to blind copy on the email. Separate email addresses with semi-colons.
Subject
The subject line.
Text box
The body of the email.