openedx / platform-roadmap

Tracking the maintenance, enhancement, and advancement of the Open edX project.
11 stars 1 forks source link

Block registration from particular countries #390

Open ayub02 opened 3 weeks ago

ayub02 commented 3 weeks ago

Abstract

Introduce a feature that allows platform administrators to restrict users from specific countries during sign-up and on account settings, addressing the need to control access based on legal, regulatory, or strategic requirements. Currently, there’s no mechanism for admins to restrict country access, requiring manual workarounds.

Detailed Product Proposal

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/4569825335/Proposal+Block+registration+from+particular+countries

Context & Background (in brief, if a Product Proposal is linked above)

The Open edX platform doesn’t currently provide a way for administrators to restrict users from certain countries. For organizations facing legal restrictions, regulatory compliance, or strategic considerations, this feature is essential to manage user access seamlessly. Currently, the country list is retrieved separately across different micro-frontends (MFEs) on the web and via a backend API for mobile apps, which leads to inconsistencies in experience across platforms.

Scope & Approach (in brief, if a Product Proposal is linked above)

The initiative focuses on modifying the country list based on a DISABLED_COUNTRIES setting, ensuring restricted countries are removed across all interfaces.

We have two implementation options:

Option 1: Maintain current structures by implementing backend filtering for both MFEs (via a new API) and mobile apps (via the registration API). Option 2: Unify web and mobile by using a single registration API for country retrieval, which requires more extensive changes to MFEs but simplifies long-term maintenance.

Value & Impact (in brief, if a Product Proposal is linked above)

Successful deployment of the DISABLED_COUNTRIES list without any technical errors across web and mobile platforms.

Milestones and/or Epics

Option 1 is too small however option 2, if selected after review, can have milestones that are yet to be defined.

Named Release

Teak

Timeline (in brief, if a Product Proposal is linked above)

Tentative plan is to implement as per available bandwidth.

Proposed By

2U

Additional Info

No response

github-actions[bot] commented 3 weeks ago

Thanks for your submission, @openedx/openedx-product-managers will review shortly.

sarina commented 4 days ago

@ayub02 I want to touch base on this ticket, there is some conversation in the proposal about implementation. I think the product direction makes sense, but we need to iron out the implementation before moving forward with approval.