One Project, Many Independent Identities
Create multiple isolated browser profiles under the same project for clean multi-account and client-separated workflows.
Why Multiple Profiles Belong in Project Management
Some projects require more than one browser identity. A marketing agency may need separate profiles for different client logins. An e-commerce seller may need distinct accounts for each marketplace region. A researcher may need separate geographic identities for localized content testing.
Multi-profile support brings those identities together under a single project while keeping them fully isolated. You manage one project definition, but each profile carries its own cookies, fingerprint, proxy, extensions, timezone, and locale.
Setting Up Profiles
Profiles are created from the project settings. You can start from a blank profile or copy an existing one. Each profile can have its own proxy configuration, browser fingerprint, and extension set. The profile manager keeps each identity organized and easy to switch.
Because profiles persist locally, logins and site preferences remain available between runs. You do not need to re-authenticate or recreate the browsing state before each execution.
Parallel Execution
When your hardware allows, you can run multiple profiles in parallel. Each profile operates independently, so one workflow does not interfere with another’s session data or page state. This is useful for batch research, client segmentation, and high-throughput data collection.
Parallel execution increases total resource use, so monitor memory and choose the number of active profiles based on your machine. The execution monitor helps you find the right balance.
Linkages with Version History and Folders
Profiles are part of the project identity. Version history records changes to project configuration, including profile-related settings. Folders keep projects organized, so a large collection of client-separated profiles remains easy to navigate.
Together, these project management features turn RTILA X from a single-script tool into an environment capable of supporting multiple clients, multiple accounts, and multiple automation products at once.