Activities of "maliming"

Hi,

All trials are the same: a Team license for 30 days with 3 support questions. Each person can only start one trial, and the company name must be unique, so your colleagues can't start another trial under MettlerToledo.

The easier way is to add them to your current organization. They first register on abp.io, then you add them by username from https://abp.io/my-organizations (open the organization, then Add New Developer in the Developers section). They will use the same trial.

If you need more developer seats or more time to evaluate, please contact us here: https://abp.io/contact

Thanks

Hi,

Right. An Admin can't give themselves any permission they don't already have, either directly or through their role. Adding the admin role to themselves is also ignored.

Changing a role's permissions also needs the AbpIdentity.Roles.ManagePermissions permission. Even if you give it to the Admins, they can still only grant the permissions they have.

Thanks

Hi,

This is supported since ABP 10.2.0. A user who is not in the admin role can only grant the permissions they have, and can only assign the roles they are in. Users in the admin role can grant everything.

So in each tenant you can set it up like this:

  1. Super Admin: the tenant's admin user. It has the admin role, so it can grant every permission available to the tenant.
  2. Admins: create a role, for example manager, and give it the permissions these admins should have, including AbpIdentity.Users.Create, AbpIdentity.Users.Update and AbpIdentity.Users.ManagePermissions. Don't add these users to the admin role.
  3. When an Admin opens the Permissions dialog of a user, only the permissions the Admin has can be checked. Other permissions are ignored when saving.

The same rule applies at every level. If an Admin gives AbpIdentity.Users.ManagePermissions to a user, that user can also grant only the permissions they have.

If you have more questions about this, please create a new question so we can track it separately.

Thanks

Hi,

Yes, add it to both. AuthServer serves the login/register pages, the register API and the Account settings API. AdministrationService returns the setting values to the UI through the application configuration endpoint.

Thanks

Hi,

  1. If you remove the two pairs from the template, the next generation rebuilds both cards from the template. Your edits in the cards are overwritten, and the markers are removed from the page too. Edits in inner blocks that are still in the generated page, like block-11 in the filters, are kept.

  2. Yes, this works:

  • Back up or commit the page.
  • Remove the two pairs from the template, save it and generate the child entity.
  • Copy only your own edits from the backup into the new page, so the new child tab stays.
  • Put the pairs back around the two cards in the template and the page, then save the template.

While the cards are protected, Suite doesn't change them at all. New child tabs, filters and columns aren't added there, so repeat the steps above when you need them. If you rename or remove a property that the cards use, the cards keep the old name and the page won't build until you update them. The template is used by all entities in the solution, so only generate this entity while the pairs are removed.

Thanks

Hi,

No, you don't need it. Just use one of the two options in my reply, the appsettings.json setting or the AccountDefaultsSettingDefinitionProvider class. You don't need both.

Thanks

Hi,

You can change the default value of this setting. Then the host and all tenants, existing and new ones, use false, unless a tenant already has its own value saved in the Settings page.

The simplest way is appsettings.json:

"Settings": {
  "Abp.Account.IsSelfRegistrationEnabled": "false"
}

Add it to every app that serves the login/register pages or the account APIs. For example, if you have a separate AuthServer, add it to both AuthServer and HttpApi.Host.

If you prefer code, add this class to your Application project. ABP picks it up automatically:

using Volo.Abp.Account.Settings;
using Volo.Abp.Settings;

namespace MyCompanyName.MyProjectName.Settings;

public class AccountDefaultsSettingDefinitionProvider : SettingDefinitionProvider
{
    public override void Define(ISettingDefinitionContext context)
    {
        var selfRegistration = context.GetOrNull(AccountSettingNames.IsSelfRegistrationEnabled);
        if (selfRegistration != null)
        {
            selfRegistration.DefaultValue = "false";
        }
    }
}

The AuthServer project doesn't reference the Application project. So if you have a separate AuthServer, add the same class there too.

Thanks

Hi,

The lines after the two </Card> tags in your template are opening markers again. A closing marker needs the / before suite-custom-code-block, so Suite can't find the pairs and regenerates both cards.

In Frontend.Blazor.Page.Item.razor.txt, replace the marker lines around the two cards with these pairs. I use 14 and 15 here so they don't clash with block-11, which may already be in your filters template from my first reply. If 14 or 15 is already used, pick other free numbers between 1 and 19.

@*//<suite-custom-code-block-14>*@
<Card>
    ...
</Card>
@*//</suite-custom-code-block-14>*@

@*//<suite-custom-code-block-15>*@
<Card>
    ...
</Card>
@*//</suite-custom-code-block-15>*@

The first pair goes around the search card and the second around the data grid card. Keep the card contents as they are and click OK to save the template.

Then put the same pairs around the same two cards in your existing .razor page. If the button or column is missing from that file now, copy it back from your backup or source control: the button inside the search card, the column inside <DataGridColumns>. If the button has a click handler, put it in .Extended.razor.cs.

Keep "Customizable code" enabled, regenerate and check the page diff.

Thanks

: )

Hi,

The example below uses block-14 and block-15, because block-13 was used for the extra columns in my last reply. If you already use any of them, pick other free numbers between 1 and 19.

  1. Select your solution on the Templates page, choose Blazor and edit Frontend.Blazor.Page.Item.razor.txt. Add the markers around the search card and the data grid card, then click OK:
@* ************************* SEARCH ************************* *@
@*//<suite-custom-code-block-14>*@
<Card>
    ...
</Card>
@*//</suite-custom-code-block-14>*@

@* ************************* DATA GRID ************************* *@
@*//<suite-custom-code-block-15>*@
<Card>
    ...
</Card>
@*//</suite-custom-code-block-15>*@

Only add these four lines. Keep everything between them as it is.

  1. Back up your existing .razor page, then add the same four lines around the same two cards in it. Without this, your current changes in these cards are overwritten the first time.

  2. If your Reset click handler or other code is in the generated .razor.cs file, move it to .Extended.razor.cs. The .razor.cs file is still regenerated.

  3. Keep "Customizable code" enabled and regenerate. Check the page diff after the first run.

After this, Suite reuses the existing cards on the page. This applies to every page in the solution that uses this template, and an entity with "Customizable code" turned off loses both cards. As mentioned before, new filters, grid columns and child entity tabs need to be added by hand.

Keep the blocks that are already inside these cards where they are in the template. Moving one of them out of the cards leaves two copies in the page.

Thanks

Showing 1 to 10 of 12958 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v11.1.0-preview. Updated on November 20, 2026, 13:33
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.