From 3b2a718092504851ddee6978287807594391298a Mon Sep 17 00:00:00 2001 From: Martin Schroschk <martin.schroschk@tu-dresden.de> Date: Fri, 10 Mar 2023 13:14:33 +0100 Subject: [PATCH] Allocation of non-primary group workspaces --- .../docs/data_lifecycle/workspaces.md | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md index fe02076e8..d8372e2d7 100644 --- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md +++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md @@ -473,8 +473,20 @@ anymore. When a workspace is created with the option `-g, --group`, it gets a group workspace that is visible to others (if in the same group) via `ws_list -g`. -The [page on Sharing Data](data_sharing.md) provides -information on how to grant access to certain colleagues and whole project groups. +!!! hint "Chose group" + + If you are member of multiple groups, than the group workspace is visible for your primary + group. You can list all groups you belong to via `groups`, and the first entry is your + primary group. + + Nevertheless, you can create a group workspace for any of your groups following these two + steps: + + 1. Change to the desired group using `newgrp <other-group>`. + 1. Create the group workspace as usual, i.e., `ws_allocate --group [...]` + + The [page on Sharing Data](data_sharing.md) provides + information on how to grant access to certain colleagues and whole project groups. !!! Example "Allocate and list group workspaces" -- GitLab