Permission definitions define which platform objects you want to grant access to, as well as the level of access that should be granted. There are many levels of permissions that can be granted, as detailed in the topics below:

  • Row security
  • Field security
  • Action security
  • Application security
  • Workflow data and transition security
  • Org unit security
  • Permission Definitions application
  • Permission Access Granted Inquiry application
  • Permissions Where Used application

Once permission definitions have been created, they can be assigned to one, or many, role definitions. The role definitions are then assigned to users to grant the permissions. Learn more in Security and Work fields.

Learn more in Roles and Security.

Row security

Row security permissions controls the level of access a user has to a table. You can filter what records a user sees, and define what type of data mutations they can perform in the table. Additional permissions may also be necessary to access tables depending on what type of data they contain. 

Row security is configured in the Row Security Rules subtable in the Permission Definitions application. You must define either a security group or table in a row security profile, you cannot define both. While row security is primarily configured on a security group, you may need to configure it on individual tables. 

For example, if you want to limit the tables a user has access to, or grant broader access to tables, in a security group. If a user should only have update access to the header to transition workflow and they don't need update access to the details, you could configure a permission to only use a specific table. 

With row security you can grant user access to either all records in the table, or you can filter it. Specify filters using either specific tables or security groups. When you filter using security groups, only records that contain the filter field are shown to a user. If a table within a security group does not have the filter field, the user does not see those records. 

Enable row security

Define a field value or a value of a related field brought in through a table lookup to enable row security. 

You can use a related field to grant access to Table B which has a table lookup field for Table A. This grants access to rows in Table B based on the value stored in Table A.

For example, the ContactNotes table stores notes about contacts in the Directory table. The security built for ContactNotes uses related table fields to grant access based on the ContactRoleGrouping in the Directory record that the note is about. This allows system administrators to grant one user access to notes about suppliers and another user access to notes about customers.

Additionally, row security can also grant exclusive access. When exclusive access is granted, a user is given access to all records in the table except where the specified filter is satisfied. In this context, it’s important to remember that the Nextworld security model is additive. If one permission grants access to something, another permission cannot remove that access.

Dashboard permissions

In addition to the standard permissions that are created, there are special permissions that need to be configured when you grant or restrict access to dashboard pages or dashboard sites.

Although dashboard pages are delivered as metadata, their security is treated as business data. In order to grant access to see a dashboard on their home page, a user needs read access to the DashboardPages table. In order for users to have access to dashboard sites, they need read access to the SiteBuilder table. 

To control which dashboards are granted, the Row Security page in the Permissions application should be configured to use the data items and list lookups that are specific to dashboard pages and dashboard sites. The list lookups contain values that pertain to specific audiences. 

For example, one value for the dashboard pages list lookup might be AP. If there are several dashboard pages that exist for members of the AP team, all that needs to be done to grant access is to use the AP dashboard grouping within the Dashboard Page Builder application.

Learn more in the Dashboard page permissions configuration and Dashboard site permissions configuration topics.

Dashboard site permissions configuration

Dashboard site permissions are configured by system administrators and application developers. Both the dashboard site and the dashboard pages within the site have their own user roles configured for permissions.

Users who are granted permissions for the dashboard site can still only see and access the dashboard pages they have permissions for. Different users may have access to different pages within the configured site. 

List lookup

If your dashboard site isn't using an existing site group, you must create a lookup key for it in the List Lookup application. If your dashboard site uses an existing site group, you can navigate to the Dashboard Site Builder application directly. 

To create a new lookup key, navigate to the List Lookup application, select the SiteGrouping record, then add a new Lookup Key for your site group. 

Dashboard Site Builder

In the Dashboard Site Builder application, select the Site Group you created in the List Lookup application or select a preexisting one. 

Permission Definitions

In the Permission Definitions application, create a new record and add an Access Rule on the Row Security page with the following details:

FieldValue
TableSiteBuilder
Filter FieldSiteGrouping
Filter ValueThe  list lookup value you created or selected for the group of dashboards a user accesses.

Role Definitions

In the Role Definitions application,  add your dashboard site permissions to a new or existing role.

Users

In the Users application, add the role for every user that requires access to the dashboard site.

Dashboard page permissions configuration

System administrators and application developers configure dashboard page permissions in the List Lookup Definitions, Dashboard Page Builder, and Permission Definitions applications. This ensures users can view dashboard pages based on their Nextworld roles.

Before configuring dashboard permissions, decide how you would like to group your dashboard pages together based on which users should see which dashboard pages.

List lookup Definitions

In the List Lookup Definitions application, you must navigate to the DashboardPageGrouping record, then add a new Lookup Key for each of your user groups. 

Dashboard Page Builder

In the Dashboard Page Builder application, configure each of your dashboard pages by setting the Dashboard Page Group to the value you created in the List Lookup Definitions application.

Permission Definitions

In the Permission Definitions application on the Row Security page, add an Access Rule with the following details:

FieldValue
Security Group
sysDashboardPages
Filter Field
DashboardPageGroup
Filter Value
The  list lookup value created for the group of dashboards a user accesses

Role Definitions

In the Role Definitions application, add your dashboard page permissions to a new or existing role.

Users

In the Users application, add the role for every user that requires access to a group of dashboard pages.

Field security

Field security deals with hiding or disabling certain fields. Field security can use filters to apply restrictions on a field based on the value in it or a related field. If one permission grants access to something, another permission cannot remove that access.

To set up field security, you must begin by creating a restricted field profile through the Restricted Field Definitions application. Use a restricted field profile to define the fields from a single table that you want to be restricted. Restrict fields on a field-by-field basis by hiding, disabling, and/or partially concealing fields. There are no limits to how many restricted field profiles can be set up for a single table, but it is a good practice to group fields, or list them within the same restricted field profile, if they are intended for a single audience. 

For example, in the Directory application the Primary Phone field and the Phone Number subtable are defined in a single restricted field profile. This is because it makes logical sense that if the user is able to see a primary phone number, then they should also be able to see any additional phone numbers captured in the Phone Numbers subtable.

Grouping fields can also present some challenges. When fields are grouped in a profile in the Restricted Field Definitions application and that profile added to the Field Security page in Permission Definitions, a security administrator must make a decision to give a user read, update, or delete access to all or none of the fields in the profile. 

Action security

Action security controls user access to run logic blocks, add attachments to records, and export records through the export action that is embedded in applications. Action security controls are found on the Action security page of the Permission Definitions application.

Logic Blocks

Logic block security is configured in the Logic Blocks subtable. Security can be applied to a single logic block, or to a security group which encapsulates multiple logic blocks. There are also additional security options that are configured during logic block configuration. Logic blocks can be configured as Private, Public-Secured, or Public. Learn more in Logic block security options.

Logic blocks configured as Public enforce the user's row, field, and workflow security. Users need access to the tables being read or modified through a logic block. 

Logic blocks configured as Public-Secured enforce action security. If no action security is configured, user permissions are applied. This includes workflow restricted fields. 

Action security consists of the following options:

  • Full Read Access—When selected, logic blocks are granted full read 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.
  • Full Update, Insert, Delete Access—When selected, logic blocks are granted full update, insert, and delete 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.
  • Apply Org Unit Security—When selected, Org Unit security is applied when the logic block is run. Row security and workflow security are still disabled. If the user has another permission for the logic block that does not apply Org Unit security, Org Unit security is not applied, even if this checkbox is selected. 

Logic block security always runs on the security of the first logic block. If Logic Block A is Public-Secured and calls logic blocks B and C, then logic blocks B and C run with the same security as logic block A. This includes the ability to bypass security limitations.

System Actions

Action security grants access to system actions including generations, attachments, and exports. All three of these system actions can be granted based on either a security group or a table. 

There is an existing role in all developer role hierarchies that allows developers to generate all objects in all security groups, so that permission is not necessary to maintain.

Attachment permissions allow a user to view and modify attachments on a record using the Attachments row action.

Export permissions allow a user to use the Export to CSV form action that exports the existing data in the application to .csv file. Exports still maintain a user's org security so they are not able to export records that they don't have access to.

Application security

Application security controls application access. With application security, you can hide an application from the menu so that a user can't launch it from that location. 

Define either the security group or the specific application that you want secured. Setting up application security for a security group is sufficient for users to be able to launch all of the apps in that security group. 

Workflow data and transition security

Workflow data security permissions control a user’s ability to see and interact with data based on the workflow state or state type combination. Workflow transition security permissions grant a user permission to perform secured transitions for a specific workflow.

See Workflow security for more information on securing workflow through the Permission Definitions application. 

Permission Definitions application

System administrators use the Permission Definitions application to create permission profiles. These profiles grant user groups access to view or change information in tables, run logic blocks, launch applications, interact with and transition workflow, and gain access to records with specific org units. 

Once permissions have been created, they must be assigned to roles. Once permissions are assigned to a role, users who are assigned that role are granted the permissions. Learn more in Roles and Security.

Each page of the application is used to assign different permissions. You can assign the permissions to a security group, or to the specific object or record referenced in the subtable. 

Row Security

Configure permissions for accessing a table's data. You can specify a single table, or a security group which the table is contained in, then select the RUID access this permission grants on the table. 

Field Security

Configure permissions for restricted field profiles. Only base restricted field profiles can be included in permissions.

Action Security

Configure permissions for logic blocks, system actions, or audit tables. Security rules only apply to Public-Secured logic blocks. Public-Secured logic block can be granted Full Read access or Full Update, Insert, and Delete.

Agent Security

Configure permissions for agents. Add a row for each agent or security group that should get access to run secured agents. A user can run a secured agent only if they have a role that includes a permission granting access to it. An agent is secured when Secure Agent is selected in the Agent Builder record. 

Application Security

Configure permissions for applications. If a user does not have Application access, that application's menu item will not appear on the Navigation Menu. 

Workflow Security

Configure permissions for workflow security profiles. 

Org Unit Security

Configure permissions for org unit security. Specify either a table name, org unit, or both. If an org unit is selected, you must specify the org unit permission type. This determines if permissions are applied to all org units for the selected table, or only the org unit selected in the row.

Permission Access Granted Inquiry application

Security developers and systems administrators use the Permission Acess Granted Inquiry application to identify which permissions grant access to specific objects on the Nextworld Platform.

To use the application, select the type of object in question in the Access Type field.

You can filter for a list of permissions that grant access to a specific:

  • Logic Block
  • Application
  • Application Setting
  • Agents
  • Menu Item
  • Table
  • Workflow
  • Restricted Field Profile

The results from this application can be used in the Permissions Where Used application to determine which role or roles must be assigned to a user to grant access to the desired Nextworld metadata object.

Permissions Where Used application

Security developers and system administrators use the  Permissions Where Used application to identify which roles use a specific permission. 

To review a list of the roles that have a specific permission assigned to them, enter the permission name in the Permission field.

Once a valid permission has been entered, the detail table populates with a list of roles that explicitly reference this permission. The list does not include roles that inherit the permission through  the role hierarchy.