Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UC] Group/organization MUST be able to be a data owner #38

Open
hzbarcea opened this issue Dec 14, 2024 · 1 comment
Open

[UC] Group/organization MUST be able to be a data owner #38

hzbarcea opened this issue Dec 14, 2024 · 1 comment
Labels
triage Issues needing triage usecase LWS Use Case

Comments

@hzbarcea
Copy link
Contributor

As a community, organization, enterprise - group in general sense
I want to be a data owner,
So that I can have control over my data.

Preconditions:

  • n/a

Trigger:

  • n/a

Actors:

  • group
  • group members with delegated rights

Distinction:

  • Defining the mandatory roles within the organization and possibly the rights that can be delegated

Github uses a similar model and it is probably sufficient for LWS needs. More specifically, any group (organization in the github case) has one or more owners that are the highest level of privileges to act on behalf of the group. We may want to identify other possible roles with more limited privileges, such as accepting access grant requests.

Scenario:

  • A community of cyclists wants to share data about upcoming tours, past timing results, tips about fixing bicycles, etc with its members.

Alternative case(s):

  • n/a

Error scenario:

  • n/a

Acceptance Criteria:

References:

@hzbarcea hzbarcea added triage Issues needing triage usecase LWS Use Case labels Dec 14, 2024
@srosset81
Copy link

I created a related use case #102 but I see it is included in this one so feel free to close it.

Regarding this scenario:

A community of cyclists wants to share data about upcoming tours, past timing results, tips about fixing bicycles, etc with its members.

I see two scenarios:

  • The data is created on the group storage and thus automatically available to all group members
  • The data is created on the storage of one member and shared with the group. The permission given to the group must then extend to all group members.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issues needing triage usecase LWS Use Case
Projects
None yet
Development

No branches or pull requests

2 participants