# Remove Demo Data (Users, Groups, ..)

**URL:** <https://forum.flowable.org/t/remove-demo-data-users-groups/12239>\
**Category:** Flowable Application\
**Created:** [May 6, 2025, 8:17am UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239 "2025-05-06T08:17:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.flowable.org/u/espen)\
**Post date:** [May 6, 2025, 8:17am UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239/1 "2025-05-06T08:17:50Z")

</div>

Hi

We’re about to go live with our Flowable Setup, but realized that we still have demo users, groups and whatnot bootstrapped into the system. We’re using OAuth.

I have skimmed through this: [Auto deployment overview | Flowable Enterprise Documentation](https://documentation.flowable.com/latest/develop/be/auto-deployment)

But I can’t find a configuration property to disable, nor a guideline on what IDM assets can/should be removed and how to remove them after they’ve been bootstrapped already.

Any help is appreciated, thanks!  
Espen

---

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.flowable.org/u/espen)\
**Post date:** [May 6, 2025, 8:43am UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239/2 "2025-05-06T08:43:13Z")

</div>

Ok, it seems that the users are deployed from the default tenant in `flowable-platform-default-idm-models-3.17.4.jar!/com/flowable/tenant-setup/default/default-tenant-setup.json`

There are several properties that can be configured it seems:

> **[Multi-tenancy | Flowable Enterprise Documentation](https://documentation.flowable.com/latest/admin/installs/mt#the-default-tenant)**
>
> Multi-tenancy is the ability of the system to cope with multiple tenants. Such a

But what is recommended for a production setup?

`flowable.platform.idm.deploy-default-resources=false` ?  
`flowable.platform.idm.minimal-setup=true` ?

And what do I need to cleanup from the DB after deploying the defaults?

---

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.flowable.org/u/espen)\
**Post date:** [May 6, 2025, 9:33am UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239/3 "2025-05-06T09:33:43Z")

</div>

Answering my first question:  
`flowable.platform.idm.deploy-default-resources=false`  
`flowable.platform.idm.minimal-setup=true`

This bootstraps:

User Templates:

- user-admin
- user-default

Users:

- admin

Groups:

- flowableAdministrator
- flowableUser

All demo users and all unnecessary groups are not bootstrapped.

This should be the default when nothing is set. Flowable needs to change this. Bootstrapping users with test passwords as a default is not secure.

---

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.flowable.org/u/espen)\
**Post date:** [May 7, 2025, 3:05pm UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239/4 "2025-05-07T15:05:34Z")

</div>

And here’s the code to remove already bootstrapped demo data:

```auto
/**
 * Removes demo data bootstrapped by Flowable:
 * com.flowable.platform.tenant.TenantBootstrapper#TenantBootstrapper(boolean)
 * com.flowable.platform.tenant.TenantBootstrapper#setupTenants()
 */
@Slf4j
@Component
public class IdentityCleanupService {

    public static final List<String> DEMO_USERS = List.of(
            "jessica.adams",
            "shane.bowen",
            "anne.barton",
            "roger.black",
            "lilly.garden",
            "sunny.flower",
            "kenny.cole",
            "ben.snow",
            "james.cox",
            "mike.miller",
            "trevor.jones",
            "emma.gant",
            "peter.schmid",
            "lisa.schmid",
            "annie.austin",
            "stephen.springer",
            "oliver.morgan",
            "ella.martin",
            "clark.kent",
            "lois.lane",
            "amanda.long",
            "boris.blue",
            "david.davidson",
            "pippa.pepper",
            "tim.lee",
            "ryan.morrison",
            "sophie.may",
            "admin",
            "operation.admin"

    );

    public static final List<String> DEMO_GROUPS = List.of(
            "client",
            "clientLookup",
            "externalUser",
            "employee",
            "employeeLookup",
            "clientAdvisor",
            "clientSupporter",
            "reporting",
            "complianceOfficer",
            "operationAdmin"
    );

    public static final List<String> DEMO_USER_DEFINITIONS = List.of(
            "user-client-supporter",
            "user-compliance",
            "user-client-advisor",
            "user-reporting",
            "user-temporary",
            "user-external-client",
            "user-client",
            "user-operation-admin"
    );

    private final IdentityService identityService;
    private final UserDefinitionService userDefinitionService;
    private final ContentService contentService;

    public IdentityCleanupService(IdentityService identityService, UserDefinitionService userDefinitionService, ContentService contentService) {
        this.identityService = identityService;
        this.userDefinitionService = userDefinitionService;
        this.contentService = contentService;
    }

    @EventListener(ApplicationReadyEvent.class)
    public void cleanup() {

        // takes care of removing memberships as well
        // See com.flowable.idm.engine.impl.persistence.entity.GroupEntityManagerImpl#delete
        DEMO_GROUPS.forEach(id -> {
            if (identityService.createGroupQuery().groupId(id).count() > 0) {
                identityService.deleteGroup(id);
                log.info("Deleted group '{}'", id);
            }
        });
        DEMO_USERS.forEach(id -> {
            PlatformUserEntity user = (PlatformUserEntity) identityService.createUserQuery().userId(id).singleResult();
            if (user != null) {
                if (user.getAvatarId() != null) {
                    contentService.deleteContentItem(user.getAvatarId());
                    log.info("Deleted avatar for user '{}'", id);
                }
                // Removes other related resources as well:
                // See com.flowable.idm.engine.impl.persistence.entity.UserEntityManagerImpl#delete
                identityService.deleteUser(id);
                log.info("Deleted user '{}'", id);
            }
        });

        DEMO_USER_DEFINITIONS.forEach(key -> {
            var def = userDefinitionService.getUserDefinitionByKeyAndTenantId(key, "");
            if (def != null) {
                userDefinitionService.removeUserDefinition(def.getId());
                log.info("Deleted user definition for key '{}'", key);
            }
        });
    }
}

```

Beware that this also deletes the `admin` user, but keeps the `user-default` and `user-admin` user templates that can be used in OAuth2 setups to map to users.

---

<div class="post-metadata">

**Author:** ![espen](https://avatars.discourse-cdn.com/v4/letter/e/b5a626/32.png) [@espen](https://forum.flowable.org/u/espen)\
**Post date:** [May 20, 2025, 11:49am UTC](https://forum.flowable.org/t/remove-demo-data-users-groups/12239/5 "2025-05-20T11:49:27Z")

</div>

And if you need to deploy custom resources, you need:

```auto
flowable.platform.idm.deploy-custom-resources=true
flowable.platform.idm.deploy-default-resources=false

```

The minimal setup will ignore those resources. As a consequence we had to copy the minimal resources into our classpath.

There’s definitely room for improvement here.
