Setting up Switch users

How does it work?

If a user connects to the Switch Server through the Switch Web Portal, through the legacy SwitchClient, or through Remote Designer, he must enter a user name and a password. The user name identifies the user to the server and grants him access based on his permissions. For example, if a Remote Designer user has read-only access, he will be able to view all flows and settings, but he will not be able to change anything.

Users or groups?

If several users should have the same permissions (for example because they have the same role), you may consider to group them and define their (access) rights at group (or "role") level. This will save you time if something changes. For example, if a new employee with a particular role enters the company, you can simply add the new user to the appropriate group.

Example:
  • Group 1: Administrators having access to all Submit points and Checkpoints. Only this group has full access to Remote Designer.
  • Group 2: Operators having access to all Submit points and Checkpoints, but with limited access to Remote Designer.
  • Group 3: Customers having access to particular Submit points and Checkpoints (so they can only see their own jobs), but with no access to Remote Designer.

With this setup, you have to configure the permissions and access rights only three times, instead of e.g. x times (with x being the number of users).

Note: In case of conflicting permissions, the highest permission level is taken into account. For example, if a user has no access to Remote Designer, but the group(s) he belongs to does have access, he will have access as well.

If you have configured a group, you can define a group manager for that group. Group managers can view jobs of their group members, whereas regular group members can only see their own jobs (unless otherwise configured).

How to configure users?

There are different ways to set up users: