If you're part of more than one workgroup, here’s a simple overview of how external mounted storage, SFTP credentials, secure access, hidden collaborators, and privacy are managed.
Can Users Be Part of Different Workgroups in Different Organizations?
Yes. Users belong to workgroups, not organizations. For more information on how to manage user accounts, see Managing User Accounts.
How Do Client-Mounted Storage and SFTP Credentials Work with Multiple Workgroups?
Each workgroup has its own Rhino Agent. Sometimes a workgroup shares a Rhino Agent with others, and sometimes it doesn’t. If you belong to multiple workgroups, the information you see in the FCP will come from the workgroup you’re currently active in.
SFTP
If your workgroups use different Rhino Agents, you’ll see different SFTP details. If they share the same Rhino Agent, the SFTP information might be the same. For more information see Adding Data to your Rhino Federated Computing Platform (FCP) Client using SFTP.
Client-Mounted Storage
If your workgroups have different client-mounted storage destinations, the client-mounted storage details will differ. If they use the same client-mounted storage, you’ll see the same information. For more information see Importing to and Exporting Datasets from Your Network Storage.
How Does Secure Access Work with Multiple Workgroups?
Secure Access works only if the active workgroup you’re using has access to the data you need. For more information see What is Secure Access?
How Do Hidden Collaborators Work with Multiple Workgroups?
Hiding collaborators is set at the project level. If it’s enabled, you’ll only see your own workgroup and the primary workgroup within a project, based on which workgroup you’re active in. Otherwise, you’ll be able to see all collaborators as usual. For more information see Permissions (Hide Collaborators).
How Does Privacy Work with Multiple Workgroups?
By default, users are part of only one workgroup. To join another workgroup, a Rhino Staff member or the second workgroup’s Workgroup Admin needs to add you. For more information, see Managing User Accounts.
When you view objects in the system, your permissions depend on the workgroup you’re acting as. For example, if you’re in a project with two workgroups (A and B), and you’re an Admin of A but a Member of B, you won’t be able to perform admin actions on objects belonging to workgroup B.