All the steps and configs are not shown while creating an inbox. So after creating an inbox user could be shown a link to do further setting and configs.

This demo is great and help us a lot.

As now JWT ( JSON Web Token ) becomes an important way of authentication. What bout adding JWT authentication to this demo? Or we use JWT authentication instead of traditional session-cookie way.

Let's make this demo more powerful. : )

Describe the solution you'd like

Resizable table columns so that you can view longer strings completely

Additional context

Thank you for your feature request – we love each and every one!

Problem
Right now any user with a valid auth token can retrieve any tag resource as long as they know the ID of the resource. We should return a 404 (Not found) error if someone tries to retrieve/update/delete a resource that does not have a matching account_id

Solution
In the show, update, and delete methods of the tag controller, let's add an authorize plug (middleware)

Context

• This is part of release-1.5 #148
• MEDIUM priority task

Tasks

• Remove dependency bcrypt-nodejs in package.json
• Add dependency bcrypt in package.json
• Migrate file app/data/user-dao.js to bcrypt
• Validate the instalation with the local test
• Add and submit the chang