How can I add permission to users by default at their registration time?

[sturlath]

Hi

I want to give all (self) registered user a default set of permissions/access. That permissions will be used to show e.g. different menus that Tenant/Host see.

So the question is : how can I hook into the "user was created" event and add the permission to the user?
Or is there some better way?

[realLiangshiwei]

https://docs.abp.io/en/abp/latest/Local-Event-Bus#events-with-past-tense

You can subscribe to user-created domain events

[sturlath]

I’ll create a project for you np but until then here is some explanation on what I'm doing.

This is a SaaS marketplace (not sure if that’s the right word). Concert holders create a Tenant and create (none-specific-Tenant) events. Ordinary (un-logged in) users can browse list of events from every Tenant in the system and sign up (and pay for) to those events.

Tenants and Ordinary users have different access (different menus). The Tenant needs to manage events and see graphs etc but the Ordinary user see his/her upcoming payed events and payment history/info etc.(and lot more).

And then its me the Host that will be managing the system.

So when an Ordinary user registers (after e.g. clicking on an event) that he/she wants to attend I want to distinguish them from a Tenant or a Host. That's why I’m trying to add permissions on after-created.

Is there another way I can accomplish this or am I trying to use the Tenant system incorrectly?

If you still need a CLI project let me know and Ill email it to you later.

[sturlath]

For (circular) reference I updated an old support question I had (3 months ago). It feels like this belongs there (since it got so complicated and not just off the bat SetForUserAsync() call..

[sturlath]

@realLiangshiwei? Do you still need a project or is isnt it clear what I’m trying to do? Is this not a known use case? It must be…right?

[realLiangshiwei]

Yes I need a project to understand your problem

[sturlath]

You got mail!

[sturlath]

We got this solved and it was related to me using a separate identity server. I created a docs PR that you can view to better understand this. Hopefully this update prevents somebody else going through my pain also ;-)