From this article you will learn:
- How to set up test and production environment
- How to switch to production (paid) subscription
- How to manage multiple organizations in Rossum
It only takes a few clicks to get started with Rossum. Go to Rossum registration page, enter your email address, and fill out a simple form.
Add all the information, and you are ready to try out our platform and technology.
So now you’ve tested the basics and want to get serious about Rossum. You’re probably wondering what the best practice is for migrating a test environment to production.
The short answer is that we make it simple!
How to set up test and production environment
When you register an account at https://rossum.app/registration, you create your Rossum account in the cloud. We call this an organization. It is a basic unit that you can further subdivide to accommodate different document processing workflows or environments.
You have two main options to separate your test environment from your production environment:
- Create two workspaces within one organization, and designate one of the workspaces as Test and the other as Prod.
- On the sign-up page, create two separate organizations and designate one of them as Test and the other as Prod.
In both cases, you will initially have access to the same Rossum Cloud as well as the platform’s features and capabilities. There are, however, subtle differences between the two approaches that you should take into account in the long run.
Compare the two options and select the one that best suits your needs
|Two separate organizations
|Two workspaces in one organization
|You create a Rossum user by adding their email address to the organization. If you need the same person in both environments, they must use an alias email for the second one and a different username (for example, John.Doe2@yourcompany.com)
|You can easily manage user access per queue with an organization. A user can have access to all queues in Test and none in Prod. Note that Admin users have access to all queues in all workspaces.
|You can’t move objects between organizations. Suppose you need a replica of a test queue in your production organization. In this case, you need to recreate the schema, queue setup, or any extensions semi-manually.
|You can easily assign existing extensions to new queues, copy the schema between queues, or quickly move queues between workspaces.
|You can’t share any objects between organizations. As a result, for each new organization, you must create new hooks, etc.
|You can attach the same extensions to multiple queues in different workspaces within one organization.
|Data integrity controls
|Users access production and test with different credentials, reducing the possibility of human error affecting production.
|Users with admin access have full visibility and unlimited access to all workspaces, queues, and documents.
|You can use any of the features included in your subscription in both test and production workspaces. However, if you have 2 separate organizations, please discuss any features you need in Test with your Customer Success Manager.
|You can easily set up the same features in both workspaces.
How to switch from test to production (paid) subscription
Suppose you choose to have a single organization with multiple workspaces serving as different environments. In that case, our billing system will associate the entire organization with your paid subscription.
If you choose to have a separate test organization, it will be a trial organization. It is free to use for up to 300 documents per month. Please note your test organization may be blocked if you exceed this limit. Inform your Customer Success Manager at Rossum about all organizations you use to ensure you have access to the capabilities you require in your test organization.
Since the transition to a paid subscription happens quietly in the background, it will have no effect on your app experience.
How to manage multiple organizations in Rossum
You can also benefit from the option to manage multiple organizations in Rossum under a single organization group. In case you want to learn more about this functionality, read this article.