# Overview ## Discussion **We should choose between developing a general-purpose auth system or a more complex auth system.** General authentication would cover things like: * Users * Permissions: Binary (yes/no) flags designating whether a user may perform a certain task. * Groups: A generic way of applying labels and permissions to more than one user. * A configurable password hashing system * Forms and view tools for logging in users, or restricting content * A pluggable backend system A more complex system would cover: * Authentication against third-parties (OAuth, for example) * Object-level permissions ## Planned Features Briefly, authentication verifies the user, and authorization checks what that particular person is allowed to do. These are some of the very basic features which we are planning to include. * User model * Permissions: Binary (true / false) * Password hashing system * Password strength checking --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://marathon-1.gitbook.io/marathon/session-management/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.