Tips: signing-in best practice

(0) Share

Report

Posted on by apangeles

252

Hi everyone,

Seeking advice from the community on how I could best go about the signing-in step of users to our website. Upon signing in, the user will obviously not have an account associated with the contact. Account association is very important as we require user inputs to associate their form submissions with a particular contact.

My dilemma is for a user experience stand point, I don't want the users logging in to their newly created account and cannot do anything inside the website. What would you recommend me doing to avoid this step?

Should I create a Power Automate when an item is created automation, notifying us, then us setting up their account then giving them an invitation? This is what I'm thinking, but is this an acceptable way of giving accounts to our users? Obviously it will take some time for us to validate the account, identify the appropriate account, assign roles, etc.

Help?

Thanks in advance

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

poweruser38 4 on at

Like (0)

Report
Copy link

Link copied!

We had similar kind of requirement, and instead of having OOB registration widget, we created an anonymous account insert page and validated with details properly (email, account number etc.,) and on creation of account, we issued user name and password with an auto number as username and random string as password.
In your case, if you want to continue with your OOB registration page, you can associate an empty account to your contact with status, may be profile needs to be updated, and create a new profile page, with account as edit form and record source type as "Record associated to current portal user " and choose the company relationship name on the basic form and force user to complete the profile with "Authentication/Registration/ProfileRedirectEnabled" site setting, Update the field "Profile Modified On" on contact once your portal profile is updated.

Was this reply helpful? Yes No
ragavanrajan 7,044 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @apangeles

First and foremost, local authentication is not recommended by Microsoft. Please use Azure AD B2C going forward. This is the future preferred authentication by Microsoft. Official link here:

You can also consider the suggested method from @poweruser38

Maybe try this way if you are interested:

1. Set custom web roles and web page access control rules and restrict all pages except the profile page.

In this way, you can prevent your new user surfing through your power pages.

2. Also, once the contact is signed up, you can deactivate the contact immediately using Power Automate /workflow and notify the admins.

3. Then the admin can assign an appropriate web role and associate an account. ( You can also do this via automation using "relate/unrelate" action.

Have fun.

Hope it helps.
------------

If you like this post, give it a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Was this reply helpful? Yes No
Fubar 8,501 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Please clarify, you mention Account, but it is unclear if you mean Account record or the Portal User?
If you just need a Portal User to be able to do stuff, then use the Authenticated User, Web Role - the privileges in this Web Role are inherited by all logged in users (it does not need to be directly assigned to specific users)

If you mean you will have multiple Portal Users that belong to the same Organization (Account) and they need to be able to see stuff from other Portal Users that belong to the same Organization you can still make use of the Authenticated Users Web Role, but they will not get access via the Organization (Account) until they are associated to the Organization (Account) and the Portal has Synced (this usually takes a up to a few minutes, but the SLA is 15 mins).

Was this reply helpful? Yes No