Getting started with Rossum takes only a few clicks: go to https://elis.rossum.ai/registration, enter your email address, fill out a simple form – and voila, you can try out our platform and our technology.
If you’ve tested the basics and you want to get serious about Rossum, you’re probably wondering what’s the best practice for having a test environment with Rossum and how you’ll migrate from test to prod environment in the future.
The short answer is, we make those things easy!
Setting up production and test environment
When you register an account at https://elis.rossum.ai/registration, you create your Rossum account in the cloud. We call this an organization. It is a basic unit that you can divide further to accommodate different document processing workflows or even environments.
To separate your test environment from your production environment, you have 2 main options:
- Create two workspaces within one organization, and designate one of the workspaces as Test and the other as Prod.
- Create two separate organizations from the sign up page and designate one of them as Test and the other as Prod.
In both cases, you initially have access to the same Rossum cloud and the same features and capabilities of the platform. There are subtle differences between the two approaches, though, and you’ll want to consider them for the long term.
| Two separate organizations | Two workspaces in one organization | |
| User access | You create a Rossum user by adding their email address to the organization. If you need the same person to be part of both environments, they’ll have to use an alias email for the second one and have a different username (such as John.Doe2@yourcompany.com) | You can easily manage user access per queue with an organization. A user may have access to all queues in Test and no queues in Prod. Note that admin users have access to all queues across all workspaces. |
| Migrate setup | Objects cannot be moved between organizations, so if you need a replica of a test queue in your production organization, you’ll have to recreate the schema, queue setup or any extensions semi-manually. | You can assign the existing extensions easily to new queues, copy the schema between queues or move queues between workspaces easily. |
| Manage extensions | No objects can be shared between organizations, so you need to create new hooks, etc. for each new organization. | You can attach the same extensions to multiple queues in different workspaces within one organization. |
| Data integrity controls | Users will access production and test with a different set of credentials, which minimises the risk of human error affecting prod. | Users with admin access have complete visibility and unlimited access to all workspaces, queues, documents. |
| Features | You can use any and all features available on your subscription, both in test and in production workspaces. If you have 2 separate organizations for that, please discuss any features you need in Test, with your Customer Success Manager. | You can easily setup the same features in both workspaces. |
Switching to production (paid) subscription
If you choose to have a single organization with multiple workspaces serving as different environments, the entire organization will be associated with your paid subscription in our billing system.
If you choose to have a separate test organization, it will be a trial organization, which you can use free of charge for up to 300 documents per month. If you exceed this limit your test organization may be blocked. To ensure you have access to the capabilities you need in your test organization, please inform your Customer Success Manager at Rossum about all organizations you use.
Migration to a paid subscription happens silently in the background and won’t impact your experience on the app in any way.
