The security option also determines how other permissions associated with a record are applied when the logic block runs. These related permissions are:
- Row security—Row security profiles are configured in the Row Security Rules subtable in the Permission Definitions application, and indicate the level of access users have to a single table, or to related tables, applications, settings, and logic blocks associated with a security group. The permissions can be applied to the whole table, or be filtered to to parts of it, and determines user's ability to read, update, insert, and delete. Learn more in Row security.
- Security Group—Security groups are configured in the Security Group Definitions application, then can be referenced in tables, applications, logic blocks, and application settings that should have the same security. This allows security to be assigned to the entire group, rather than individual objects. Learn more in Security groups.
- Action security—Action security is configured in the Logic Blocks subtable in the Permission Definitions application, and controls a user's access to run logic blocks. When securing logic blocks, you can grant access to run a single logic block, or all logic blocks in a specific security group. Action security only applies to
Public-Securedlogic blocks. If no action security is configured, user permissions are applied. Learn more in Action security.
The table below details how a logic block interacts with other logic blocks, and how permissions are applied to the logic block, based on the value selected in the Security Option field.
| Security Option | Notes | Permissions Applied |
|---|---|---|
Private logic blocks must be called by endpoints or other logic blocks. If called by another logic block, it must be in the same product family as the calling logic blocks. These logic blocks generally have a very specific purpose and should not be used or called in other instances. For example, the Accounts Receivables applications have logic blocks built for currency calculations. These logic blocks should only be used in that product family and associated applications. Marking the logic blocks as | The logic block inherits the security of whatever logic block called it. | |
Public logic blocks can be called from anywhere. | Public logic blocks can only be accessed by users with the correct permissions. Each user's individual row security determines what they can do in the application. For example, one user may have standard read, update, insert, and delete access for the table which the logic block is written over. This user would be able to perform any actions associated with these functions in the application. Another user may only have read permissions in their row security and would get an error message if they attempted any actions that require update, insert, and delete access. Row security permissions are required for all tables which the logic block accesses. Users may have different read, update, insert, and delete access on calling logic blocks and processing logic blocks which can limit their access. Workflow security, restricted field security, and Org Unit security are honored and applied. | |
Public-Secured logic blocks can be called from anywhere. | All security is bypassed as long as the user has access to the initial table or logic block, or if they have access to the security group that the logic block or table are part of. Logic blocks are granted full access to the tables which they read and write from, without needing explicit row, field, or workflow permissions to the tables being read or modified. This means that the logic block can perform whatever actions it needs to run, regardless of whether the user has explicit permission for each of the actions. This is useful when a transaction needs to update a field that the current user isn't allowed to see or use, but is related to their job function. Workflow security and restricted field security are bypassed by calling the logic block to insert, update, or delete records with the appropriate action security checkboxes selected. Org Unit security is bypassed by default, but optionally can be applied in the Permissions application. If no action security is configured, user permissions are applied. If a user's row security grants them more access to the table than a selected security group is granted, the user retain their access. For example, if a security group only has read access, but a user has update, insert, and delete access, the user would retain their full access. |
For more information, see Logic block security option best practices.
Logic block security option best practices
These best practices ensure that the Security Options field in the Logic Block Builder application is configured with the correct Public, Public - Secured, or Private option.
The Security Option field controls how and when a logic block can be run. Learn more about these configurations in the Logic block security options topic.
Use the table below to determine which privacy setting to use based on the setup and type of logic block.
When choosing between Public and Public-Secured, by default we should use Public whenever possible. Do not use Public-Secured unless necessary. The use case of why it needs to bypass security should be thought out and it should not be blindly changed to Public-Secured. Adding a Public logic block to an existing feature may require additional security permissions to execute. Consult with your security point of contact if your use case requires additional access other than read-only.
| Logic Block Type/Function | Called From | Called Across Families | Configuration | Additional Considerations |
|---|---|---|---|---|
| Any Type | Any source | Yes | Public |
|
| Transaction or Validation | Any source | Yes | Public-Secured |
|
| Transaction or Validation | Logic block | No | Private |
|
Learn more about the different types of logic blocks in the Logic block types topic.