Permissions for Software Content Management Users

ThingWorx Utilities Administration > Permissions for Software Content Management Users

The following table provides the user groups that Software Content Management users must be a part of, to perform administrative tasks:

User Group

Description

TW.RSM.RemoteServices

Users with access to the remote access actions such as File Transfer, Deployments, and Remote Connections.

Users in this group will also be a member of the TW.RSM.RemoteAssets user group.

You must add any user group that you create to the TW.RSM.RemoteServices user group so that the user group gets all the appropriate visibility permissions detailed in this section.

TW.RSM.RemoteAssets

Users with access to view all TW.RSM.ManagedAsset assets.

TW.RSM.Admin

Users with administrative access to Software Content Management.

TW.RSM.EdgeDevices

Users representing edge devices.

This user group must be used, along with a non-admin application key, for C SDK-based agents which use Software Content Management.

In some cases, you may want to limit the visibility of assets through Software Content Management to certain users or organizations. In this case, you need to complete the following tasks:

• Step 1: Create user groups and assigning users

• Step 2: Create the organization structure

• Step 3: Assign users and groups to the organizational units

• Step 4: Add user groups to the TW.RSM.RemoteServices user group

• Step 5: Provide visibility support for non-administrator users

For example: You can set up different user groups in ThingWorx Composer to control visibility to specific menus and pages of Software Content Management. For example, you can create a group to specify users that should be allowed to create and test packages (view the Packages menus). You could also create a group to specify users that should be able to perform production deployments (view the Deployments menus).

Was this helpful?