[Catalog] Restrict Enrollments Based on Domain

[jsowalsk]

Hi everyone,

Much like the feature that got pushed out in theserelease notes, we would like the ability to restrict enrollments at the subcatalog level based on domain and not just the registration like the current feature. Due to our institution having people create non-institution (Non-UMD) accounts through a registration form on our registration page outside of Catalog the current feature is not working as expected. We still need to customize course cards to reflect who can enroll in Catalog courses because even though someone creates a Non-UMD account they still may have the ability to register for the course if they so choose since no one is blocking them from enrolling besides an indicating message that we place on the course card (as you see below).

In addition, for the current feature, if you choose a domain such as gmail.com then all of the gmail.com accounts will be blocked or allowed. It should be that email addresses such as 123456@gmail.com (with the specific name of the email address) can be blocked or allowed.

[bromanski]

Yes I vote up this feature request.

[danielcktan]

I vote for this as well.

There should be an option for us to totally turn off registration and account creation as our Canvas is meant for inhouse use and not open to the public.

We are able to turn off registration and account creation at Canvas but the registration feature at Catalog overwrites Canvas'.

[ProductPanda]

Comments from Instructure

As part of the new Ideas & Themes process, all ideas in Idea Conversations were reviewed by the Product Team. Any Idea that was associated with an identified theme was moved to the new Idea & Themes space. Any Idea that was not part of the move is being marked as Archived. This will preserve the history of the conversations while also letting Community members know that Instructure will not explore the request at this time.