Datasets

Datasets let you prepare realistic sample data without changing your live organisation. Each demo, sandbox, or training dataset is isolated from Production.

Non-production datasets don’t send email. You can still see in-app notifications and test workflows, forms, invitations, and other features, but Runnit suppresses their email delivery. Password reset and email verification messages for your Runnit account still work.

Organisation owners and administrators can open Admin > Datasets.

Create and switch datasets

To create a dataset:

1. Enter a New dataset name.
2. Choose Demo, Sandbox, or Training.
3. Select Create and switch.

Use the buttons under Active dataset to move between Production and your other datasets. A dataset that’s still seeding or has failed can’t be selected.

The switcher lists only the datasets that belong to the workspace you’re signed in to. If you belong to several workspaces, each workspace’s site shows its own datasets. When the list covers more than one organisation, for example a client workspace with its own datasets, each button is prefixed with the organisation name.

Impersonating a teammate keeps your current dataset: if you’re in Production when you start acting as another user, you stay in Production. You return to your own active dataset when you end impersonation.

Seed sample data

1. Switch to the dataset you want to seed.
2. Choose the number of employees. The allowed range is 10 to 300.
3. Select Seed dataset. If the dataset already contains generated data, the button is labelled Re-seed dataset.
4. Wait for the seed to finish. The page updates the employee, project, task, time-entry, and last-seeded details.

Re-seeding replaces the active dataset’s staff, clients, projects, tasks, schedules, time entries, rates, and generated assets. It also moves generated dates so they’re anchored to today.

Generated projects are spread across a useful demo horizon. Some begin up to two weeks before the seed date, while delivery dates extend up to two months after it. The portfolio includes draft, active, review, client-review, and completed work.

Each project has a client-aware brief with a realistic objective, audience, deliverables, channels, measures, and approvals. Its milestones and tasks fall inside the project dates, and task descriptions refer to deliverables in that brief. Draft-project schedules and resource bookings are marked tentative; bookings for other project states are confirmed.

Caution

Re-seeding is permanent for the selected dataset. Check the active dataset name before you continue.

Production overrides

Production replacement is restricted to the specifically authorised production-data owner. Other owners and administrators must switch to a non-production dataset before they can seed data.

For the authorised account, the page shows Override production dataset and an acknowledgement checkbox. The button stays disabled until the warning is accepted. The override keeps that account’s existing login password, but replaces the Production data described above.

An impersonated session can’t run a Production override.

Client assets are isolated

Generated datasets don’t connect demo clients to Production asset collections. They create separate client records, separate brand collections, and fresh generated assets inside the selected dataset. Re-seeding a demo dataset rebuilds those demo records without changing or linking to Production records.

Next, see Client Organisations to learn how clients, teams, and shared assets work in a live organisation.