MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Foundation

User Management

Sign in, manage your profile and preferences, and control active sessions — with the security controls an algo-trading platform requires: verified email, server-tracked sessions, and a daily-logout discipline.

Where you will find this

Login (email + Google), 2FA / session (daily-logout aware), Onboarding wizard / first-run, User administration, User detail & sessions, Preferences & defaults.

Purpose

User Management is the front door. It handles registration and email verification, password and Google sign-in, your profile and trading preferences, and the sessions that keep you signed in — each one tracked on the server so it can be revoked the moment you log out.

Daily logout & 2FA

In line with the SEBI/NSE retail-algo framework, sessions are designed around 2FA and a daily-logout discipline. You re-authenticate each trading day before algos can act on your behalf. [Confirm exact cadence against your broker + current SEBI circulars before go-live.]

The User Management module provides authentication, user profile management, session management and user administration for MyAlgoGuru.

It serves as the identity foundation for the application and governs user access to all business modules.

Objectives

The module will:

  • Authenticate users.
  • Manage user accounts.
  • Maintain user profiles.
  • Support secure access to the application.
  • Manage authenticated sessions.
  • Support broker account ownership.
  • Provide a foundation for future role-based access control.

Functional Scope

The module includes:

  1. User Registration
  2. User Authentication
  3. Email Verification
  4. Password Management
  5. User Profile
  6. Session Management
  7. Broker Account Ownership
  8. User Administration

Deployment Model

MyAlgoGuru is deployed as a dedicated application instance for each customer.

Each customer receives an independent deployment.

User Management operates independently within every deployment.

Users belonging to one deployment does not have visibility into another deployment.

User Registration

The platform will support new user registration.

Users may register using:

  • Google Authentication
  • Email and Password

Registration will create a new user account within the current deployment.

Email Verification

Users registering through Email and Password will verify their email address.

The account remains unverified until email verification is completed.

Only verified accounts is permitted to authenticate.

Authentication

The platform will support:

  • Google Login
  • Email Login

Successful authentication will create an authenticated user session.

Authentication failures does not create a session.

Password Management

The platform will support:

  1. Forgot Password
  2. Password Reset

Password reset will require successful user verification before a new password becomes active.

User Profile

Every user will maintain a profile.

The profile includes:

Mandatory

  • Name
  • Mobile Number

Optional

  • Gender
  • Avatar

The platform will support international mobile numbers including country codes.

You can update their profile information.

User Session

Authenticated users will have an active application session.

The platform will support:

  • Login
  • Logout
  • Session Validation
  • Session Expiry

Only authenticated sessions is permitted to access protected business modules.

Broker Account Ownership

Every authenticated user is able to configure broker accounts.

A user may configure multiple broker accounts.

Broker accounts may belong to different broker providers.

The User Management module will maintain ownership of configured broker accounts.

User Administration

The platform will support basic user administration.

Authorised users is able to:

  • View Users
  • Enable User
  • Disable User
  • View User Details

User deletion does not permanently remove business records created by that user.

Historical ownership and audit information is preserved.

User Status

Every user will maintain an operational status.

Supported statuses include:

  • Pending Verification
  • Active
  • Disabled

Only Active users is permitted to authenticate.

User Preferences

The platform will maintain user-specific preferences independently of authentication.

Preferences may include future capabilities such as:

  • Default Broker
  • Default Trading Product
  • Notification Preferences
  • Language
  • Time Zone
  • Dashboard Preferences

Business Rules

  • Every user will belong to exactly one application deployment.
  • Email registration will require email verification.
  • Only verified users is permitted to log in.
  • Every authenticated user will have an active session.
  • Users may update their own profile.
  • Users may configure multiple broker accounts.
  • Users may configure broker accounts across multiple broker providers.
  • Disabled users does not be permitted to authenticate.
  • User deletion will never remove historical business records.
  • Historical ownership will always be preserved.

Audit Requirements

The platform will maintain an audit trail for user management activities.

Audit information includes, where applicable:

  • User Registration
  • Login
  • Logout
  • Email Verification
  • Password Reset
  • Profile Update
  • User Enable
  • User Disable

The audit trail will preserve historical records.

Out of Scope

The following are outside the scope of this module:

  • Broker Authentication
  • Trading Permissions
  • Strategy Permissions
  • Risk Limits
  • Portfolio Management
  • Order Management
  • Role-Based Access Control (to be covered in a future module)

Roles, access and expiry

Access is default-deny. Four roles stack rather than replace each other, so a user holds the sum of what they have been granted and nothing more. Accounts are seeded by an administrator — there is no self-signup on a trading node.

  • An access expiry outranks a role: once a user’s access has expired they are refused, even holding an admin role.
  • A read-only user never trades live. What read-only may do is one explicit surface rather than a scattering of individual checks.
  • Logging out revokes the session on the server, so a stored token alone cannot keep acting.

Granting premium indicators and strategies

Administration → Premium Strategies is a grid: rows are the premium indicators and strategies, columns are the non-admin users, and every cell starts unchecked. A premium item is invisible and unusable to a user until their cell is ticked. Admins hold every premium item without a grant and are not columns.

What the gate can and cannot promise

Anything the server computes is refused by id for a user without the grant. A chart study’s maths, however, runs in the browser — so hiding it controls what a user is offered rather than what a determined user could compute. It is worth describing it that way rather than as absolute.