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

New User Process #1042

Closed
adriancollier opened this issue Jan 20, 2015 · 1 comment
Closed

New User Process #1042

adriancollier opened this issue Jan 20, 2015 · 1 comment
Assignees
Milestone

Comments

@adriancollier
Copy link
Contributor

We need to ensure that we have a stable process for bringing new users onto the platform.

Problems with the current process:

  • Everyone from Akvo gets an email
  • Not certain who is responsible for approving
  • All done via email outside of RSR
  • No overview of pending or rejected users

With the v3 changes we have split up the new user process into 2 sections. Creating an account and connection to an organisation.

Create a new account

  • A new user signs up on RSR
  • User receives an email with a link
  • User clicks on link
  • Account is activated1

Connect to an organisation

  • A user requests to be added to an organisation
  • A message is sent to the correct admins2
  • Admin confirms or declines the user within the MyRSR section
  • An email is sent to the user to confirm the action and informing them of the admin that carried this action out

1 An activated account can log in and view elements within RSR, but has no permissions on any project so cannot create, edit or update any content.

2 A correct Admin is determined by one of the following:

  • Being an administrator for the organisation
  • Being an administrator for the organisation that is the content owner of the organisation the user registered to
  • Being an administrator with the support option enabled3

3 A new option should be created on the user that allows them to be defined as a support user. This should only be used for Akvo Staff, and this will determine if they have access to all organisation data and not just their own network. If the support option is not selected then no new user emails are received.

Additional elements:

  • Add a comment field to the Employment record that Akvo and Partner admins can use to mark the status of the registration. E.g. Requested confirmed from Head Office on 1-3-2015, awaiting response.
  • We need to ensure we have content for the following emails:
    • New account
    • Confirmed registration
    • Employment request (to Partner Admin)
    • Employment request (to Akvo Support Admin)
    • User employment approved
    • User employment declined
@adriancollier adriancollier added this to the RSR v3 milestone Jan 20, 2015
@KasperBrandt KasperBrandt modified the milestone: RSR v3 Jan 20, 2015
@KasperBrandt KasperBrandt self-assigned this Mar 9, 2015
kardan added a commit that referenced this issue Mar 12, 2015
@kardan kardan closed this as completed Mar 12, 2015
@KasperBrandt
Copy link
Contributor

Test plan

GIVEN the RSR admin
WHEN a User is viewed as a superuser
THEN it is possible to set this user as support user

GIVEN the user management page
WHEN an RSR admin with support user rights visits the page
THEN all users should be visible

GIVEN the user management page
WHEN a user visits the page
THEN the page is paginated

GIVEN the user 'join organisation' process
WHEN a user requests to join an organisation
THEN all RSR admins with support role will get an email
AND all organisation user management or admins with support role will get an email

@MichaelAkvo MichaelAkvo moved this to Done in RSR Dec 8, 2022
@MichaelAkvo MichaelAkvo added this to RSR Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

3 participants