Ticket #212 (new enhancement)

Opened 16 years ago

Last modified 14 years ago

use a reviewing process to register users

Reported by: disabled-hc@… Owned by: janguenot
Priority: P2 Milestone: CPS 3.5.7
Component: CPSDefault Version: TRUNK
Severity: normal Keywords: user

Description (last modified by fguillaume) (diff)

use a review process to register users

Following #202 and Benoît's comment on #165 and a late discussion with Julien, should we consider a reviewing process to register users ?

When a user registers, its account should wait for a validation to be activated. The benefits are that the member's folder will be created with the reviewer's rights, so the workflow won't get annoyed. Of course, the usual benefits of reviewing apply.

But we have to take care to write e-mail templates in the user's language.

Change History

comment:1 Changed 16 years ago by disabled-hc@…

  • Cc ja@… removed

comment:2 Changed 16 years ago by disabled-hc@…


  • fills in and validate the join form;

maybe it's time to add other fields to that form, like first and last names,

prefered language (or taken from what Localizer says);

  • gets an e-mail informing him that it's account has to be activated.

Administrator or any user with the "Add portal member" permission:

  • gets an e-mail informing him a new account awaits for reviewing;
  • refuses this account, the user is informed by e-mail and the account is deleted;
  • or accepts this account, creates a member's folder for the user with its

admin rights (so the workflow doesn't complain). the user is informed by e-mail.


  • can use its name/password to log in.

To know wether an account is validated, should we add a state property containing 'private' or 'public' or a simple boolean value?

comment:3 Changed 16 years ago by fguillaume

  • Cc fg@… added

See also #296.

comment:4 Changed 15 years ago by disabled-hc@…

Dolce and IDG-CIO have an implementation using a CPSDocument for each pending user.

comment:5 Changed 14 years ago by janguenot

  • Version changed from 3.4.0 to TRUNK
  • Milestone changed from unspecified to CPS 3.4.0

comment:6 Changed 14 years ago by fguillaume

  • Description modified (diff)
  • Milestone changed from CPS 3.4.0 to CPS 3.5.0
Note: See TracTickets for help on using tickets.