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

Enforce "Org Confirmation" When Selecting/Switching to Some Orgs #970

Open
aaronskiba opened this issue Dec 20, 2024 · 0 comments
Open

Enforce "Org Confirmation" When Selecting/Switching to Some Orgs #970

aaronskiba opened this issue Dec 20, 2024 · 0 comments

Comments

@aaronskiba
Copy link
Collaborator

aaronskiba commented Dec 20, 2024

This point was raised by Don Stuckey in the `"roadmap-devs" channel of the "roadmap" group on Slack:

hi @here
in DMPonline, it is possible for any user to assign themselves to any organisation (without authenticating with that org) and therefore see any org's plans;
i understand this is a core design principle in roadmap, as it allows researchers to easily switch their org when they move to another org, and so i understand it is the same in DMPopidor, DMPAssistant, and DMPTool;
however, we have recently had concerns raised by orgs that are not comfortable with any user being able to set themselves to their org and then see their org's plans (and see say names and email addresses of contributors / collaborators of the plan);
so i was wondering if any of you guys have had similar concerns raised, and if so, how have you addressed them with respect to the design and purpose of the core roadmap application code?

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

No branches or pull requests

1 participant