Separate Automatic Account Approval for Internal and External users

James Von Alamag shared this idea ago

Needs Review

Separate Automatic Account Approval into two.

One is for Internal users or any users that fall under the domain. One is for external users that doesn't.

Different layers for each, one where a input box that list what is classified as an internal domain could work as well.

I like this idea

Replies (1)

Guest ●

Thanks for your feature request.

Can I ask for some more detail, to make sure I understand what you need? so please let me know if you have any additional context that you’d like to add!

Reply URL

Guest ●

Thanks for reaching out,

I’ll track this with our team internally, and let you know!

URL

James Von Alamag ●

Hi Nitin,

Please factor in that this stems from the current limitation of Importing LDAP users. So the customer is using Automatic Account Approval to add Internal and External users to the system as workaround. Because the Automatic approval feature has no process to disassociate internal and external users they're forced to add External users as Full access at the onset as well (this workaround unfortunately doesn't work well with our Seat Licensing structure).

Adding this feature would solve their issue.

URL