- 5 minutes to read

DefaultRolesInViews – System Parameter

Streamline Log View creation with the DefaultRolesInViews system parameter in Nodinite. This setting determines which Roles are automatically assigned when administrators create new Log Views, reducing manual configuration and ensuring consistent access policies.

What you'll achieve with this parameter:

  • Automatically assign roles when creating new Log Views
  • Reduce administrative overhead and save time
  • Ensure consistent access policies across Log Views
  • Support multiple default roles with semicolon separation

The DefaultRolesInViews System Parameter defines which Roles are pre-selected when a Nodinite administrator creates a new Log View. Rather than manually selecting roles each time, the specified default roles are automatically included, streamlining the Log View creation process.

System Parameter Name Data Type Values/Example Comment
DefaultRolesInViews string Administrators Default = Administrators. Use semicolon (;) to separate multiple roles.

This parameter is used by the Web Client when administrators add a new Log View. The default roles appear in the Roles section of the General tab, ready for the administrator to configure permissions or add additional roles as needed.

Note

Changes to this parameter are effective immediately in the Web Client. You do NOT need to restart any services for the new value to take effect.

How It Works

When a Nodinite administrator creates a new Log View:

  1. Click Add Log View - Navigate to Log Views Overview and click the Add Log View button
  2. General Tab - Enter name, description, and other basic information
  3. Default Roles Pre-Selected - The roles specified in DefaultRolesInViews are automatically added to the Roles section
  4. Configure Permissions - Administrator sets permissions (View Context, View Body, Resend, etc.) for the default roles
  5. Add More Roles - Optionally add additional roles beyond the defaults

This automation ensures that critical roles (typically Administrators) always have access to newly created Log Views, while allowing flexibility to add role-specific permissions as needed.

Multiple Default Roles

You can specify multiple roles by separating them with a semicolon (;). For example:

Administrators;IntegrationTeam;SupportStaff

All specified roles will be automatically added when creating a new Log View. The administrator can then configure individual permissions for each role according to the Permission Set for Log Views.

Best Practices

✅ Always Include Administrators - Ensure the Administrators role is always in the default list to maintain administrative access
✅ Add Common Business Roles - Include roles that need access to most or all Log Views (e.g., Support, Operations)
✅ Keep the List Focused - Only include roles that truly need default access; specialized roles can be added manually
✅ Document Your Standard - Maintain documentation of which roles should have access to different types of Log Views

Example Configurations

Minimal (Default)

Administrators

Best for: Organizations with diverse Log View requirements where most views need custom role assignment.

Standard Operations

Administrators;Operations;Support

Best for: Organizations where operations and support teams need broad access to business transactions.

Enterprise Multi-Team

Administrators;IntegrationTeam;BusinessAnalysts;CustomerSupport;Compliance

Best for: Large organizations with many teams requiring different Log View access patterns.

When NOT to Use Many Default Roles

❌ Highly Specialized Log Views - If most Log Views serve specific teams or purposes, fewer default roles reduce unnecessary access
❌ Security-Sensitive Environments - Where principle of least privilege requires explicit role assignment for each view
❌ Different Access Patterns - When Log Views vary significantly in their audience and purpose

Frequently Asked Questions

Find more solutions and answers in the Nodinite System Parameters FAQ, as well as the Troubleshooting user guide.

How do I change the value?

Changing a value for the pre-defined System Parameters is described in the generic 'How do I change the System Parameters' article.

Do I need to restart anything?

No! Changes to this parameter are effective immediately in the Web Client. Administrators will see the updated default roles the next time they create a new Log View. No service restart is required.

Can I remove roles after they're added by default?

Yes! When creating a Log View, the administrator can remove any of the default roles or adjust their permissions in the General tab. The DefaultRolesInViews parameter only controls which roles are pre-selected - it doesn't enforce them.

What happens if a role name doesn't exist?

If a role name specified in DefaultRolesInViews doesn't exist in your Nodinite instance, it will be ignored when creating new Log Views. Only valid, existing roles will be pre-selected. Ensure role names match exactly (case-sensitive).

Does this affect existing Log Views?

No. Changing the DefaultRolesInViews parameter only affects new Log Views created after the change. Existing Log Views retain their current role assignments. To update existing Log Views, use the Manage existing Log View feature.

How do I configure permissions for the default roles?

After the default roles are added to a new Log View, click the Edit button in the Roles section on the General tab. Then configure the Permission Set for Log Views for each role, including:

Should I include all roles as defaults?

No. Only include roles that legitimately need access to most or all Log Views. Adding too many default roles:

  • Creates security risks by over-granting access
  • Requires more work to remove unnecessary roles from specialized views
  • Violates the principle of least privilege

Focus on core operational roles (Administrators, Operations, Support) and add specialized roles manually when needed.

Next Step

Add or Manage Log View - Create and configure Log Views
Roles - Understand role-based access control
Permission Set for Log Views - Configure granular permissions
Administration