Page History

Configuring Permissions

To configure, go to Security → Permissions and assign permissions by choosing options in the security settings menu. To do this, you must be logged in as an Administrator. To log in as the Admin, click the home icon at the top-left corner to access the Designer Workspace home page. Then press the Login button to open the Designer Workspace popup login. Enter the username as Administrator. By default, it does not require a password.

Return to the Security → Permissions, and select the Edit and Run permissions for each user group (Administrator, Guest).

Pre-defined Security Groups

The platform comes with a few predefined Permission groups that you can use, or you can create your own.

• Administrator

• Guest

• User

• Engineering

• Supervisor

• Maintenance

• Operator

Security → Tutorial | Concept | How-to Guide |  Standards Compliance | Reference

Pre-Defined Permission Groups

Seven standard groups are configured by default:

Configuration Properties

Edit Permissions

Controls access to Designer modules:

Run Permissions

Controls runtime operations:

Configuring Permissions

Access Requirements

1. Login as Administrator
2. Navigate to Security → Permissions
3. Administrator password required for changes

Setting Group Permissions

1. Select permission group row
2. Configure Edit permissions:
   • Check modules user can modify
   • Uncheck restricted areas
3. Configure Run permissions:
   • Enable allowed operations
   • Disable restricted functions
4. Save changes

Permission Inheritance

Users inherit combined permissions from all assigned groups:

User: John
Groups: Operator, Maintenance
Result: Union of both group permissions

Example combinations:

• Operator + Maintenance = Displays + Diagnostics
• Engineering + Supervisor = Development + Monitoring
• User + WebAccess = Basic rights + Web client

Runtime Permission Checks

Checking Current Permissions

csharp

// Current user's groups
string permissions = @Client.Permissions;

// Check specific permission
bool canEdit = @Security.HasPermission("EditDisplays");
bool canShutdown = @Security.HasPermission("Shutdown");

// Check multiple permissions
bool isAdmin = @Client.Permissions.Contains("Administrator");

Conditional UI Elements

csharp

// Show/hide based on permissions
if (@Security.HasPermission("StartTools"))
{
    btnDiagnostics.Visible = true;
}

// Enable/disable functions
btnShutdown.Enabled = @Security.HasPermission("Shutdown");

Security Levels

Hierarchical access control using Level property:

Usage:

csharp

// Check user level
if (@Client.Level >= 100)
{
    // Show supervisor features
}

Best Practices

1. Principle of least privilege - Grant minimum required permissions
2. Use groups not individuals - Manage through group membership
3. Document group purposes - Clear role descriptions
4. Regular audits - Review permission assignments
5. Test permission sets - Verify restrictions work
6. Separate development/operations - Different groups for each
7. Protect Administrator - Limit admin group membership

Common Permission Sets

Operator Standard

• Edit: None
• Run: ClientStart, WebAccess
• Use: Daily operations

Maintenance Technician

• Edit: EditTags
• Run: StartTools, ToolsSetValues
• Use: Troubleshooting

Shift Supervisor

• Edit: Alarms, Reports
• Run: Unrestricted except Shutdown
• Use: Operations management

System Engineer

• Edit: Unrestricted except Security
• Run: Test, StartTools
• Use: Development and testing

Troubleshooting

Cannot edit module:

• Check Edit permissions
• Verify group membership
• Confirm logged in correctly
• Not using Guest account

Runtime function disabled:

• Review Run permissions
• Check user's groups
• Verify permission spelling
• Test with Administrator

Permission not working:

• Clear permission cache
• Restart runtime
• Check group assignment
• Review permission conflicts

In this section...

Edit Permissions

It is possible to allow or deny a user to edit different modules of the Solution Designer. The available options are shown in the image below.

Run Permissions

It is also possible to allow or disallow a user to perform different actions during Runtime.

Properties Reference

The Properties References present a reference that describes and explains the properties for Security Permissions. The table lists all properties available for the configuration item. However, not all properties described in the documentation are displayed in the data grids by default. Right-click column headers to see which property columns are currently displaying. The displayed properties appear with a check mark.

The data grids allow users to manage and organize information by showing or hiding properties in tables within configuration interfaces. To turn on or off showing a property on the data grid, right-click column headers to select properties or use the reset button to return to default settings. Check out Working with DataGrids for detailed info.

Security Permissions

In this section: