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

Organisation admin #284

Open
grhammo opened this issue Aug 31, 2015 · 6 comments
Open

Organisation admin #284

grhammo opened this issue Aug 31, 2015 · 6 comments

Comments

@grhammo
Copy link

grhammo commented Aug 31, 2015

Organisation admin for a pathway assessment is limited to one user per organisation. Personally speaking it would be useful if more than one user could register per organisation.

For example, providing access to my team for our organisation, would ensure we are all able to access our baseline, and associated comments, should we be called on to recall why a maturity level was determined

This could be as simple as a view only log in if there were concerns about 'contributor' access to a completed assessment.

Can we please get this looked at? As currently if a team member leaves, so does the Organisations source to the Maturity assessment

@ldodds
Copy link
Collaborator

ldodds commented Sep 7, 2015

Thanks for leaving a comment, this is on our plans for a future update.

Just in case you weren't aware: you can currently share read-only versions of reports with colleagues. As the admin user when you are viewing a report there is an orange "share this report" button. Clicking this should give you an authorised link that will let anyone view the finalised report, including all questions, comments.

This is one way in which you can share your current base line.

@grhammo
Copy link
Author

grhammo commented Sep 14, 2015

Thanks Leigh, That's great to know. Doesn't really help us though if the admin of our account leaves the organisation. This is where a second admin would be great per organisation, just as a back-up.

We're serious about using the tool to baseline each year and grow our maturity, so having access to the original baseline would be invaluable for further analysis.

@Stephen-Gates
Copy link
Collaborator

@ldodds can you share your plans for a future release? Perhaps a link from this repository's readme.md to a roadmap document with some non-committal timings. You could even add costs so sponsors could consider funding certain functionality.

@ldodds
Copy link
Collaborator

ldodds commented Sep 15, 2015

@Stephen-Gates yes, thats a good suggestion.

@grhammo understood. my recommendation - and what I've suggested to people I've introduced the too to personally - is to use a shared email address, e.g. for a team, that can be used as the primary login. This will allow the account to be shared.

@Stephen-Gates
Copy link
Collaborator

@ldodds if a long-term solution is not likely to be provided soon then perhaps the work-around you suggest should be added to the registration page. People will naturally use their personal work email address and most organisations do not permit shared organisational emails.

@Floppy
Copy link
Contributor

Floppy commented Feb 19, 2016

This is in our 1.0 list of things to fix, mainly through #294 and #293. See https://github.com/theodi/pathway/milestones/1.0

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

No branches or pull requests

5 participants