Skip to content

Adding groups documentation - #32

Open
valentinRyckaert wants to merge 2 commits into
ElixirTeSS:mainfrom
hep-training:groups-docs
Open

Adding groups documentation#32
valentinRyckaert wants to merge 2 commits into
ElixirTeSS:mainfrom
hep-training:groups-docs

Conversation

@valentinRyckaert

Copy link
Copy Markdown

Summary of changes

Add user documentation linked to this pull request

@valentinRyckaert
valentinRyckaert deleted the groups-docs branch July 24, 2026 08:42
@valentinRyckaert
valentinRyckaert restored the groups-docs branch July 24, 2026 12:08

@PhilReedData PhilReedData left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall very good. I have made some suggestions about the language in a few places.


Groups is a feature which for now is used only to manage access of private spaces.

A user being part of a group has access to every private space which requires the group.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A user being part of a group has access to every private space which requires the group.
A user of a group has access to every private space associated with that group.

To request a new group on TeSS for your use case:

1. Select a TeSS instance for your request.
2. Prepare the following details of the new group: a title, your username and the list of users/owners of your group

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Prepare the following details of the new group: a title, your username and the list of users/owners of your group
2. Prepare the following details of the new group: a title, your username and the list of users/owners of your group.

- {fas}`clipboard-check;sd-text-success` Can exchange materials with other TeSS instances and spaces
- {fas}`clipboard-check;sd-text-success` Support from the global TeSS community
- {fas}`clipboard-check;sd-text-success` Open and public[^freespace]
- {fas}`clipboard-check;sd-text-success` Open and public[^freespace] or private (only people being in specific groups have access)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- {fas}`clipboard-check;sd-text-success` Open and public[^freespace] or private (only people being in specific groups have access)
- {fas}`clipboard-check;sd-text-success` Open and public[^freespace] or private (only people in specific groups have access)


This new feature is possible thanks to the [mTeSS-X project](../overview/mtess-x). Catalogues are pooled into a shared instance but look to their community as if they have their own catalogue with their own identity.

There are two types of spaces:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
There are two types of spaces:
There are two types of spaces, depending on the configuration of the TeSS instance:

This new feature is possible thanks to the [mTeSS-X project](../overview/mtess-x). Catalogues are pooled into a shared instance but look to their community as if they have their own catalogue with their own identity.

There are two types of spaces:
- **public space**: its resources are accessible from the outside (visible in the main catalogue with a special toggle). Anyone, logged in or not, can access it.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **public space**: its resources are accessible from the outside (visible in the main catalogue with a special toggle). Anyone, logged in or not, can access it.
- **public space** (default): its resources are visible to everybody viewing the space (and visible in the main catalogue with a filter). You do not have to be logged in.


There are two types of spaces:
- **public space**: its resources are accessible from the outside (visible in the main catalogue with a special toggle). Anyone, logged in or not, can access it.
- **private space**: its resources are not visible outside the space (even with the toggle in the main catalogue to see resources from other spaces). A private space requires being in at least one of a defined list of groups to have access to it (the list can be one or more groups).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **private space**: its resources are not visible outside the space (even with the toggle in the main catalogue to see resources from other spaces). A private space requires being in at least one of a defined list of groups to have access to it (the list can be one or more groups).
- **private space**: its resources are not visible outside the space (even with the filter in the main catalogue to see resources from other spaces). A private space requires the user to be associated with a relevant group. You have to be logged in.

I don't think we need the detail of multiple groups/lists here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants