Nextworld solutions must be shipped with security enabled through security groups, permissions, roles, and role hierarchies. Role and role hierarchies should reflect typical business processes.
Granular security groups and permissions provide flexibility in creating roles, but can make it more complicated for a customer to configure their own permissions and roles.
For org unit security, always identify the org unit field at the table level. If this field is not identified at the table level, a customer cannot implement org unit security for the table.
Always deliver workflow security to provide options for the customer to secure transitions.
Design considerations
There are several considerations when designing security, such as:
- Segregation of duties—An internal control designed to prevent fraud by ensuring at least two individuals are responsible for separate parts of a process.
- This design considerations applies to security groups, permissions, roles and role hierarchies. Construct all the pieces with enough granularity to construct roles that allow segregation of duty possible.
- Field updates—Certain groups of fields need to be secured from update. Decide where in the process they should be restricted, and whether the field should be considered private information.
- Logic block classification—Some logic blocks should be classified as public secure.
- Workflow transitions—Determine at which steps security is required, and at which steps fields can no longer be changed. Consider the different roles and who might perform specific transitions.
- Permissions based on security groups rather than individual objects—Makes the upgrade process easier as new objects are easily introduced into a security group and may not require any changes to permissions, roles, or role hierarchy.
- Security groups cannot be customized by a customer. Consider separate security groups by task or function to provide greater flexibility of separating duties. For example, a person who can enter a transaction may not have the authority to void the transaction.
Granularity
Nextworld uses a granular security model which defines who can access each part of the system, and what they can do with that access. There are several different permissions to choose from, such as:
- Read Only access
- Full RUID (Read/Update/Insert/Delete) access
- Logic block (public secured) permission with read access
- Logic block (public secured) permission with full RUID access
- Application access
- Attachment permission which includes both read and write access
- Export permission
- Audit permissions, one audit permission to view audit information for a record (restricted) and one to view all audit records (unrestricted)
Security group best practices
These best practices ensure permissions and roles are configured consistently throughout Nextworld using security groups, even when new objects are introduced into production.
When new objects such as tables, applications, or logic blocks are released into production, users must have the proper access to use them. Security groups make it easier to release objects into production, especially if customers have defined their own permissions and roles, since new objects are automatically included in security based on the group.
Security groups should be granular when creating permissions to ensure segregation of duties is possible. For example, entering a supplier and a supplier invoice and then making a payment against a supplier invoice should each have their own security groups. This allows for permissions and roles to be configured where a single person cannot perform all duties. If all were in the same security group, the customer would have to instead configure security for every individual object which requires in depth knowledge of the system.
All objects for each function should have the same security group. For example, in the same security group include the tables, applications, application settings and logic blocks to perform a single function, such as entering a supplier invoice. Keep in mind the top level logic block dictates the security for any subsequent logic blocks they call. When securing a logic block that is a common object used by more than one module, the security group on that logic block should be the same as the main table(s) that the logic block is dealing with.
Security groups for specific applications should have the name of the application in the security group name.
Write the description of the security group with the purpose of the group or a summary of what is in the group.
Restricted Field Profile best practices
These best practices ensure that permissions are configured consistently throughout Nextworld.
Create restricted field profiles for fields that should not be updated. Do not put each field in its own restricted profile unless absolutely necessary. This creates complexity and overhead for the customer to configure.
Consider the grouping of fields that naturally go together and that should be restricted together. For example, if specific users can update the birth date of an employee but not update the marital status, then the fields must be in different restricted profiles.
Workflow security best practices
These best practices ensure that workflow security, workflow restricted fields and workflow transitions are configured consistently throughout Nextworld.
Workflow security must be configured for every table which uses workflow.
Workflow security can be designed to provide for read access versus update access, based on the different workflow steps.
While restricted fields can be used at any state type, for workflows with a closed state type, add a restricted field profile to lock the fields at a closed state. In particular, lock fields that may cause data integrity issue such as dates, quantity, and amount fields.
Design Considerations:
- Map out the different roles performing the transitions. Keep in mind workflow type.
- Determine if and which fields should be locked at certain transitions
- Determine RUID access at each step based on role
- Determine which steps in your workflow are secured and required permission to perform the step.
Roles best practices
These best practices ensure that security roles and role hierarchies are configured consistently throughout Nextworld.
Roles
There are three types of roles Nextworld defines:
- Duty Roles— Describes the access a user has for a record.
- Functional Roles—Describes the task and activities a user can perform.
- Aggregate Roles—Combines multiple functional roles.
Nextworld delivers functional roles for each family and module and duty roles with varying RUID (read, update, insert, delete) access, such as:
- Accessor—Read access to data only (R) with no application access.
- Viewer—Read access to data and app access (R).
- Create—Read and insert access to data (RI).
- Updater—Read and update to data and application access to all update records (RU).
- Admin—Read, update, insert and delete access to data (RUID).
- Delete—Access to data and app access to delete records (RD).
- Export—Access to export function.
- Attachment Accessor—Access to view attachments.
- Attachment Admin—Access to manage attachments.
- Auditor—Access to view the audit history.
- RecordAuditor provides access to view the audit history for a specific record. The user must have access to the record through other permissions.
- AuditorUnrestricted provides access to view the audit history regardless if they have access to the record.
Best Practices
There are several best practices to consider, such as:
- Include the Menu Family only when the role gives access to an application. Only include the family menu where the application is included.
- Descriptions should clearly describe the role to a customer.
- Define roles at a granular level. This enables the ability to create role hierarchies that combine multiple roles as well as include one role in multiple role hierarchies.
- Duty roles should not use permissions directly from another family; a functional role can be made up of duty roles from different families.
- As a best practice,
- Duty Roles describe a task
- Functional roles comprise of Duty roles and describe a job function.
- Aggregate roles group other functional roles.
- Permissions are assigned to Duty Roles only.
- Create two functional roles specific for audit history.
- Role to view audit of the record.
- Role to view all audit history.
- Create two functional roles specifically for attachments:
- Accessor to view the attachments
- Admin to manage the attachments.
Role Hierarchy
Define role hierarchies for different functional roles and levels of functional roles. For example, define roles for the data entry level (AP Accountant), department manager (AP Manager) up through different levels of the organization (Financial manager or controller).
With Nextworld, manager and higher level roles may have only read, update and approval permissions.
Do not set duty role as a top level in the role hierarchy.
The functional roles for audit should be placed as a top level. This allows the user to assign these roles to specific users with a role.
Aggregate roles are created for companies whose personnel perform many of the functions for a department. These roles contain Admin as part of the role name.
Security best practices for dashboards
These best practices ensure that dashboard security is configured consistently throughout Nextworld.
Configure dashboard security by functional area. One or more dashboards can be assigned to the functional area.
Ensure users are granted appropriate access for each dashboard.
Use DashboardPageGrouping to make configuration of permissions and roles sustainable as new objects are introduced into production.
Permissions best practices
These best practices ensure that permissions are configured consistently throughout Nextworld. This includes row security, field security, action security, application security, workflow security and organizational (org) security.
Design Considerations
There are several considerations when designing permissions, such as:
- Segregation of duties
- If only rows for the specific user should display (use the system value _DirectoryUser)
- If your permission needs different restricted field profiles, in particular if a field is considered private information
- The granularity of permissions. Permissions are additive and can be re-used in multiple roles
- Logic blocks that are classified as public secured and whether elevated access is needed
- Map out workflow transition and determine at which steps security is required and which steps fields must be locked. Consider the different roles and who might perform specific transitions
- Descriptions should be user friendly to clearly describe the permission to a customer. (i.e. Role = arCashReceipts - R - Misc CR, Description = Accounts Receivable Miscellaneous Cash Receipts Data Accessor)
RUID (read/update/insert/delete) access
Create combinations of RUID to provide flexibility when assigning a permission to roles. Based on requirements create the following:
- Create one permission with full RUID access
- Create separate permissions for Read only access
- Create separate permission for read/insert/update (RUI) access or create separate read/insert (RI) and read/update RU)
- Create separate permission for read/insert RI) and for read/update RU)
- Create separate permission with Read/Delete, if needed
Row Security
Security groups can have multiple tables included that have a shared function. For example, there are different tables to store payment information and each table requires access in order to create a payment. Using a security group makes the permission easier to configure and understand. Nextworld delivers row security as a separate permission.
Only create permissions with a specific filter if it is common industry practice. Otherwise, create row security with your preferred RUID access and no fields or values selected. This allows customers to customize for more specific granularity, and is more performant than creating individual rows for each filter value.
Use table lookup fields and filter fields instead of storing duplicate data in your data model. For example, if you want row security based on the supplier's class code of Materials, use the table lookup field for Supplier and the filter field of SupplierClassification and the filter value of Materials (user defined). When using row security and defining a filter field, make sure an index is defined on the table. Otherwise, you could have performance issues. However, there are some caveats when the index gets used based on the data set. Learn more on Index best practices.
Restricted Fields
Critical transaction fields should be restricted once a record is in a closed state. For example, once a payment is posted, the amount fields, dates, and supplier field should not allow update. However, a note or memo field may be updated.
Action Security
For attachments and export, we recommend using security group. Nextworld creates separate permissions for attachments and exports.
For audit security, we recommend setting to be restricted (unrestricted access is unchecked) where a user can only view audit for the records they can see. Nextworld creates a separate permission for audit access, one for access is restricted and one for access is unrestricted.
For logic block access security, we recommend using the security group. Nextworld creates separate permissions for logic blocks as they are used in both entry applications and integrations. Only logic blocks that are classified as public secured must be specified in action security. Other logic block classifications can be called by any user, however, depending on the classification, a users security is applied.
Application Security
Always include your applications within a permission so the user only sees applications they have access to use. Nextworld creates a separate permission for application security.
Workflow Data Security and Workflow Transition Security
If your table has workflow defined, you must deliver workflow security. If you do not define workflow security, a user cannot perform any transitions or perform updates at certain steps.
Nextworld delivers workflow data security and transition as a separate permission. Always include a permission for workflow transition if your workflow has secured workflow transitions. Workflow transition applies to all transitions checked as Secured (all or nothing).
Org Security
For any table with an organization unit, always define the Org Field at the table level. If delivering org unit security, deliver only with the setting of User Orgs checked along with the RUID.
Org unit security best practices
These best practices ensure org unit security is configured consistently and efficiently throughout the product.
Whenever you enable or disable org unit security on a table, publish a release note that explains the change. After a table with org unit security enabled is delivered to customers, you cannot remove the org unit without approval.
Only enable org unit security on Header, Detail, or Main type tables.
If you enable org unit security on a Header table, enable it on all associated Detail tables. If Detail tables are not secure, users can build custom applications and gain access to the data. Consider adding the Header org unit field to all the associated Detail tables and enabling that org field for org unit security.
Do not enable org unit security on tables that do not permanently store data, such as report flat tables, dashboard common context, logic block tables and test harnesses tables.
For report flat tables, you should instead secure all the data source tables that the logic block fetches data from before it inserts data into the flat table.
Do not enable org unit security using org unit fields that might be empty because users cannot access these records. The only exception to this is if the org unit field is on a detail table that is automatically populated with a logic block or common context.
Setting the Apply OUS filter on Filtered Table Lookup fields
This will filter the orgs a user can select to only those they have access to. Be mindful that this will also apply the OUS filter when inserting a record to the table via logic.
The Apply OUS filter can be set on any org unit fields. The table does not have to have OUS enabled to set the apply ous filter for a field.
You should always set the Apply OUS filter on a field used to enable org unit security on a table.
Integration tables by best practice do not have filtered table lookups setup. An exception is that the Apply OUS filter should be set on org for which OUS is enabled on the integration tables, providing for filtering when records are entered manually. This filter will not cause data import restriction issues as the table is already secured for OUS.
Report versions should not be secured as the org unit field in the table is almost always an optional field and therefore can be empty. This will allow users access to all of them. When they run a report version, however, the report will only include data for org units they have access to.
Secure integration tables by org unit, just like the transaction tables.
Do not enable org unit security on module settings. Modules settings are inherited based on the company structure. Limiting the view by org unit in settings will prohibit the user from being able to view the settings configuration.
Be aware of where Public Secured logic blocks are used as they bypass all security, including org unit security. If you want org unit security enforced in public secured logic blocks you need to set up the action security permission to the logic block to indicate that.
In the base product our best practice is to move the public secured logic block to a new version of the security group it is in with Restrict on the end of the name and then add a new row to the existing permission to secure that security group with apply org unit security.
Be aware that users cannot access values from a table lookup if they do not have access to the referenced table.