Architecture User Management

User Management and Logins

Holmes will need to manage users, which will include Roles and Permissions and controlling sessions and logins.

What is a "User"?

A user is someone who has access to the CMS for purposes of managing content or other CMS-related management duties.

What a "User" isn't:

Users are not meant to be authors who happen to have CMS access levels. To accomplish something like the concept of an "Author", we would be to create a content type called "Authors" and connect to entries via a Relationship input type.

Requirements

• Add a new user
• Update an existing user
• Password management
  • User can change their own password
  • Admin can change a user's password
  • Password recovery
• Manage all users (admin-level access only)
• Delete a user
• Login and Session Management
  • connect to W3
  • User may login
  • User may logout
  • Non-signed in user password recovery options
  • Sessions to track user access
  • Research Passport JS
• Roles and Permissions
  • All levels will have login access and access to their own profile
  • Possible levels:
    1. Full access to all aspects of the system
    2. Full access to all content, but no system-wide settings or user management
    3. Full access to specific content types only
    4. Limited access to create new entry in a content type, and manage their own entries
  • Access control option
    • Have a "superuser", user 0
    • All other users are under roles with pluggable permissions (by configuration)
    • This will most likely be determined by our User MGMT system

TODO

• Flesh out User management requirements
• Research existing Node-based user management systems