Hello, our tenant will be obtained from an external form for our project. When the tenant is included in the system, a default edition assignment will be made, and we will want to control the permission statuses of this tenant. In the current scenario, we are conducting our tests by adding a tenant through the admin panel without using an external form and assigning the edition we created to this tenant.
Regarding the problem we are experiencing;
When a tenant is added to the system, role assignments are made by default. When there is no distinction in permissions for these role assignments (MultiTenancySide or RequiredFeature), all permissions are assigned to this role. However, we only want to assign permissions that contain features valid for editions assigned to the tenant to that tenant. For this reason, we use the RequiredFeature property, which you mentioned is available for permissions, to establish the connection between permissions and features. However, in this case, we encounter the following situation. We assign the edition we created with the desired features to the tenant. Afterwards, when we log into the system with the tenant assigned to the edition, we cannot access the menus included in the edition. Upon checking, we see that no record has been added to the PermissionGrant table. However, we noticed that if, for example, the Category permission exists and the project runs without adding the RequiredFeature tag to the permission beforehand, the Category permission is recorded in the PermissionGrant table for the tenant. Afterwards, when we add the RequiredFeature tag to the Category permission, we see that it works. After adding the RequiredFeature tag, we see that it works. However, when a new tenant arrives after this process, the RequiredFeature tag is present, so no record is added to the PermissionGrant table again. In short, what we want here is to be able to control the tenant's permission status on a feature-specific basis.
we kindly request your support.
thanks
Hello,
The project features I created are as described above. When I create an entity in ABP Suite, I encounter the error shown in the screenshot I attached.
I would appreciate it if you could provide a solution to this error.
Best regards.
Hello, I have a customer, my customer has customers, I want to limit the customers and users that my customer will create here, is there a place where I can do this from your interface or do you have an infrastructure for this. Good work
