Security is often easiest to overlook when building quickly, but it’s much harder to fix later. Whether you are extending Nextworld objects or building a completely new application on the platform, security should be designed intentionally and early.
Existing Resources
Before building, we strongly recommend reviewing the following:
LMS Courses
NXTP 150 - Security for Developers - 23.2: Covers foundational security concepts and best practices.
Contact the Partner Development Services team if you have questions about registration.
Nextworld Help
Overview of platform security, including advanced configuration options such as organizational unit–based security, and specific security considerations for Directory and Dashboards.
Security Matrix
Use this matrix to design and validate your security.
SecurityDesignTemplate.xlsx
General Guidance For Partners
Extending Nextworld Objects
Keep your objects in the same Security Group as the object you are extending.
Be aware of everything already secured by that group–you inherit it.
Building Your Own Applications
All standard security practices apply (LMS + Help + guidance below).
Plan security during design, not after development.
Core Security Principles
Granularity matters.
- Each permission should grant access to one and only one thing.
- For example, a permission should secure:
- A single table or security group
- A single workflow security profile
- A single logic block
- For example, a permission should secure:
- Duty roles should not contain access to multiple objects.
- Why this matters
- Easier to assign and evolve access over time
- Partners and customers can compose roles without duplication
- Avoids rework when requirements change
- Makes it easier to add roles incrementally as users gain responsibility
Security Groups: Be Intentional
- Do not share security groups
- Do not use Nextworld-owned security groups for partner-owned objects (unless they are extensions)
- Partner-owned objects (that aren’t extensions) should live in partner-owned security groups
- Keep security groups focused and small
- Example: Two apps are using the same table, where there are different groups of users that need to access each app.
- Suggested approach: Create two separate security groups
Menu Security
- Applications:
- Permissions or duty roles to app settings do nothing if the app is not secured by the menu
- Interactive reports:
- Require permission to app settings
- Are secured by the menu by default
Understanding Security Access
- A user will receive the greatest access granted by all their roles.
- Example:
- Permission 1: Read access to a table
- Permission 2: Read, Insert, Update, Delete
- Result: The user has full Read, Insert, Update, and Delete access
- Example:
- Workflow security works differently… a user receives the least access granted by their roles.
- Example:
- Permission 1: Read and Update
- Permission 2: Read only
- Result: The user has Read-only access.
- Example:
Workflow Security is Different (and Easy to Get Wrong)
- Workflow follows least access, not greatest.
- Managers often end up Read-only, even if a processor has more access.
- You must have:
- Row security to the table
- Permission to the workflow security profile
- Example:
- For an HD application, if workflow is enabled on both header and detail, you typically need:
- Header row permission
- Detail row permission
- Workflow profile permission
- For an HD application, if workflow is enabled on both header and detail, you typically need:
Workflow Restricted Field
- Workflow-restricted fields remove access; they do not grant it.
- A user will see the sum total of all restricted fields from all roles they have.
- Example:
- Role 1 restricts fields: Field 1, Field 2
- Role 2 restricts fields: Field 3, Field 4
- Result: A user with both roles sees all 4 fields restricted
- Example:
Row Security Filtering Gotchas
- If a permission grants RUID access to a security group AND includes a filtered field, the filter is pointless unless all tables in the group contain that field
- Every table in the security group must have (and populate) the filtered field. Otherwise, users will receive “Not Authorized” error
- Example:
- All tables in the arCashReceipts security group will need to have the field CashReceiptType type for this permission to allow access to the data in the table
Restricted Field Security
- Restricted fields remove access; they do not grant it.
- Behavior
- A user sees the sum of all restrictions
- Multiple roles = more restricted fields
- Full Logic Block access on a Public Secured Logic block will allow the user to update restricted fields
- Exception: Restricted field errors will still occur if an attempt is made to update the Workflow Type field, fields with auto number and locked fields, even if done from a Public Secured Logic Block
Logic Block Security: What to Know
- When securing a logic block, it is important to understand which security option to use (i.e. private, public, public-secured). Choose carefully, as your selection determines which permissions are required.
- See NW Help Topics: ‘Logic block security options’ for details on each option.
- Child logic blocks always inherit the parent’s security.
- If the parent (or first) logic block is set to Public, all child logic blocks will run as Public.
- If the parent (or first) logic block is set to Public-Secured, all child logic blocks will run as Public-Secured.
Application Links
- Users do not need permission to launch the called application
- They do need row security for data to load once launched
- You can configure your environment to show or hide application links, field, row, and form actions based on a user’s permissions.
- See NW Help Topics: ‘Hide application actions with user permissions’ for more details.
Playpen Has No Security
- Objects in Playpen ignore security rules.
- Example:
- Tables in Playpen allow full access regardless of permission
- Public-Secured logic blocks in Playpen bypass table security
- Never validate security behavior using playpen objects.
Role Picker Limitations
- Background tasks ignore the Role Picker
- All roles assigned to the user are used
- To test properly, use a user with only the intended role
Understanding Security Errors
- You’ll typically see one of three messages:
- Not Authorized
- No permission to the table or the security group
- You lack workflow security
- Missing workflow permission or insufficient workflow access
- Restricted field error
- Field access removed by restricted field rules
- Not Authorized
Final Thoughts: Plan Security Early
Security should never be an afterthought. Taking time to prioritize security ensures your solution is:
- Secure
- Easier for customer adoptions
- Easier to maintain and build on over time
If you’re unsure, engage Partner Development Services early — it’s far easier to design security correctly than to fix it later.





