Determine User Groups

In ThingWorx Navigate, user groups determine visibility (what users can see) and permissions (what users can do). They’re based on roles and the tasks users need to do in the app. Likewise, user groups limit what users can see and do.

Depending on whether you’re using OOTB apps or building a custom app, the way you define and create user groups will differ.

User groups for OOTB apps

OOTB apps have predetermined user groups that are connected to licenses. Users will either:

• Have their own named license as part of a specific user group, or
• Be part of a group in which they'll check out a license when they need to use the app.

After you install the software, you'll assign each user to one license group based on what they need to do in the app. To learn about the licensing groups for OOTB apps, review Modify ThingWorx Permissions: Users and Groups.

User groups in ThingWorx for a custom app

If you’re building a custom app, you’ll define and create your own user groups. ThingWorx also offers built-in user groups for administrators, developers, and users you could use to start.

When you’re ready to create groups, you’ll make groupings at 3 levels in ThingWorx Composer:

1. Organization
2. Organization unit
3. User group

Different user roles direct what different types of permissions you need to give to a user group. A user role is a person or group who can take specific actions in the app using specific data. For instance, a user role might be a support engineer (user role) who pulls reports (permission) for a site in Europe (visibility). Anticipate that your user groups and organization units may expand over time.

In ThingWorx, there are 3 forms of permissions you can adjust:

• Visibility permissions state what Mashups and/or dashboards a user can see. Assign visibility permissions at an organization or organizational unit level.
• Run-time permissions state what services a user can execute and what properties they can access. Assign run-time permissions at the user group level.
• Design-time permissions state what a user can modify and access in ThingWorx Composer. Assign design-time permissions at the user group level.

Your developer or development team should become familiar with ThingWorx Composer in order to create user groups. PTC has training courses available to help, such as ThingWorx: Fundamentals of Deployment.

Based on your selected use case, determine what user groups you need and who will be part of each group. Include all types of users across your organization, from admins to end users.

The project sponsor, admin, developer, and key stakeholders who are familiar with the data should collaborate to define and list user groups. Understand what your app does and what people will use it for.

Define user groups for OOTB apps

To define user groups for OOTB apps, determine:

• Which users need a permanent license
• Which users will check out a license instead of having a permanent license
• Which app(s) each type of user needs access to

Document who will be part of each user group so that your implementation team is prepared to add users after installation. This document will help you troubleshoot and manage user groups later.

Define user groups for a custom app

To determine user groups for a custom app, first document requirements for visibility (what users can see) and permission (what users can do) for each type of user. Then group users together based on similar requirements. Consider whether the built-in user groups for administrators, developers, and users may be enough to start with.

Requirements should align with your selected use case. Be as accurate as you can in your documentation. If users have too much access, they could see confidential data they should not have. If users have too little access, they may not be able to see the data they need.

Document the user groups including visibility and permissions so that your developer and admin know what user groups to create. This document will help you troubleshoot and manage user groups later.