-
Notifications
You must be signed in to change notification settings - Fork 9
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
Administrator : Redesign of the backoffice #85
Comments
You're awesome @Soulou |
Thanks =P but do you think something is missing ?! |
Should the linking between a user and a candidacy be done in the admin backoffice ? |
Yes, exactly. On May 16, 2013, at 5:51 PM, cavarelli [email protected] wrote:
|
Beautiful ! |
Not so sophisticated ^^ |
For the moment, I've created a new namespace "new_admin" in order not to delete the old yet. It'll be necessary to move it from new_admin to admin when the candidate backoffice is also finished. |
Thumbs up! |
With the candidate backoffice, we have to rethink the admin backoffice, a lot of functionnalities will became useless as admins will be able to access each candidate backoffice.
I'd like to gather everything that must be contained by the admin backoffice :
The text was updated successfully, but these errors were encountered: